From: Hao Xu <hao.xu@linux•dev>
To: io-uring@vger•kernel.org, Jens Axboe <axboe@kernel•dk>
Cc: Dominique Martinet <asmadeus@codewreck•org>,
Pavel Begunkov <asml.silence@gmail•com>,
Christian Brauner <brauner@kernel•org>,
Alexander Viro <viro@zeniv•linux.org.uk>,
Stefan Roesch <shr@fb•com>, Clay Harris <bugs@claycon•org>,
Dave Chinner <david@fromorbit•com>,
"Darrick J . Wong" <djwong@kernel•org>,
linux-fsdevel@vger•kernel.org, linux-xfs@vger•kernel.org,
linux-ext4@vger•kernel.org, linux-cachefs@redhat•com,
ecryptfs@vger•kernel.org, linux-nfs@vger•kernel.org,
linux-unionfs@vger•kernel.org, bpf@vger•kernel.org,
netdev@vger•kernel.org, linux-s390@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-block@vger•kernel.org,
linux-btrfs@vger•kernel.org, codalist@coda•cs.cmu.edu,
linux-f2fs-devel@lists•sourceforge.net, cluster-devel@redhat•com,
linux-mm@kvack•org, linux-nilfs@vger•kernel.org,
devel@lists•orangefs.org, linux-cifs@vger•kernel.org,
samba-technical@lists•samba.org, linux-mtd@lists•infradead.org,
Wanpeng Li <wanpengli@tencent•com>
Subject: [PATCH 05/11] vfs: add file_pos_unlock() for io_uring usage
Date: Sun, 27 Aug 2023 21:28:29 +0800 [thread overview]
Message-ID: <20230827132835.1373581-6-hao.xu@linux.dev> (raw)
In-Reply-To: <20230827132835.1373581-1-hao.xu@linux.dev>
From: Hao Xu <howeyxu@tencent•com>
Add a helper to unlock f_pos_lock without any condition. Introduce this
since io_uring handles f_pos_lock not with a fd struct, thus
FDPUT_POS_UNLOCK isn't used.
Signed-off-by: Hao Xu <howeyxu@tencent•com>
---
include/linux/file.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/file.h b/include/linux/file.h
index bcc6ba0aec50..a179f4794341 100644
--- a/include/linux/file.h
+++ b/include/linux/file.h
@@ -81,6 +81,11 @@ static inline void fdput_pos(struct fd f)
fdput(f);
}
+static inline void file_pos_unlock(struct file *file)
+{
+ __f_unlock_pos(file);
+}
+
extern int file_pos_lock_nowait(struct file *file, bool nowait);
DEFINE_CLASS(fd, struct fd, fdput(_T), fdget(fd), int fd)
--
2.25.1
next prev parent reply other threads:[~2023-08-27 13:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 13:28 [PATCH v6 00/11] io_uring getdents Hao Xu
2023-08-27 13:28 ` [PATCH 01/11] fs: split off vfs_getdents function of getdents64 syscall Hao Xu
2023-08-27 13:28 ` [PATCH 02/11] xfs: add NOWAIT semantics for readdir Hao Xu
2023-08-27 20:44 ` Matthew Wilcox
2023-08-29 7:41 ` Hao Xu
2023-08-29 13:05 ` Matthew Wilcox
2023-09-04 1:02 ` Dave Chinner
2023-08-27 13:28 ` [PATCH 03/11] vfs: add nowait flag for struct dir_context Hao Xu
2023-08-27 13:28 ` [PATCH 04/11] vfs: add a vfs helper for io_uring file pos lock Hao Xu
2023-08-27 20:47 ` Matthew Wilcox
2023-08-27 13:28 ` Hao Xu [this message]
2023-08-27 13:28 ` [PATCH 06/11] vfs: add a nowait parameter for touch_atime() Hao Xu
2023-08-27 13:28 ` [PATCH 07/11] vfs: add nowait parameter for file_accessed() Hao Xu
2023-08-27 21:32 ` Matthew Wilcox
2023-08-29 7:46 ` Hao Xu
2023-08-29 11:53 ` Matthew Wilcox
2023-08-30 6:11 ` Hao Xu
2023-09-03 22:30 ` Dave Chinner
2023-09-08 0:29 ` Pavel Begunkov
2023-09-10 22:01 ` Dave Chinner
2023-09-04 9:51 ` Christian Brauner
2023-08-27 13:28 ` [PATCH 08/11] vfs: move file_accessed() to the beginning of iterate_dir() Hao Xu
2023-08-27 13:28 ` [PATCH 09/11] vfs: error out -EAGAIN if atime needs to be updated Hao Xu
2023-08-27 20:51 ` Matthew Wilcox
2023-08-27 13:28 ` [PATCH 10/11] vfs: trylock inode->i_rwsem in iterate_dir() to support nowait Hao Xu
2023-09-04 9:37 ` Christian Brauner
2023-08-27 13:28 ` [PATCH 11/11] io_uring: add support for getdents Hao Xu
2023-09-04 9:57 ` [PATCH v6 00/11] io_uring getdents Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230827132835.1373581-6-hao.xu@linux.dev \
--to=hao.xu@linux$(echo .)dev \
--cc=asmadeus@codewreck$(echo .)org \
--cc=asml.silence@gmail$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=bpf@vger$(echo .)kernel.org \
--cc=brauner@kernel$(echo .)org \
--cc=bugs@claycon$(echo .)org \
--cc=cluster-devel@redhat$(echo .)com \
--cc=codalist@coda$(echo .)cs.cmu.edu \
--cc=david@fromorbit$(echo .)com \
--cc=devel@lists$(echo .)orangefs.org \
--cc=djwong@kernel$(echo .)org \
--cc=ecryptfs@vger$(echo .)kernel.org \
--cc=io-uring@vger$(echo .)kernel.org \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-btrfs@vger$(echo .)kernel.org \
--cc=linux-cachefs@redhat$(echo .)com \
--cc=linux-cifs@vger$(echo .)kernel.org \
--cc=linux-ext4@vger$(echo .)kernel.org \
--cc=linux-f2fs-devel@lists$(echo .)sourceforge.net \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-nfs@vger$(echo .)kernel.org \
--cc=linux-nilfs@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-unionfs@vger$(echo .)kernel.org \
--cc=linux-xfs@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=samba-technical@lists$(echo .)samba.org \
--cc=shr@fb$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=wanpengli@tencent$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox