From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file
Date: Tue, 22 Nov 2022 09:51:35 +0800 [thread overview]
Message-ID: <0c6a44ff-409e-99b2-eaa9-fd6e87a9e104@linux.alibaba.com> (raw)
In-Reply-To: <20221120210004.381842-1-jlayton@kernel.org>
Hi,
On 11/21/22 4:59 AM, Jeff Layton wrote:
> The file locking definitions have lived in fs.h since the dawn of time,
> but they are only used by a small subset of the source files that
> include it.
>
> Move the file locking definitions to a new header file, and add the
> appropriate #include directives to the source files that need them. By
> doing this we trim down fs.h a bit and limit the amount of rebuilding
> that has to be done when we make changes to the file locking APIs.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> fs/9p/vfs_file.c | 1 +
> fs/afs/internal.h | 1 +
> fs/attr.c | 1 +
> fs/ceph/locks.c | 1 +
> fs/cifs/cifsfs.c | 1 +
> fs/cifs/cifsglob.h | 1 +
> fs/cifs/cifssmb.c | 1 +
> fs/cifs/file.c | 1 +
> fs/cifs/smb2file.c | 1 +
> fs/dlm/plock.c | 1 +
> fs/fcntl.c | 1 +
> fs/file_table.c | 1 +
> fs/fuse/file.c | 1 +
> fs/gfs2/file.c | 1 +
> fs/inode.c | 1 +
> fs/ksmbd/smb2pdu.c | 1 +
> fs/ksmbd/vfs.c | 1 +
> fs/ksmbd/vfs_cache.c | 1 +
> fs/lockd/clntproc.c | 1 +
> fs/lockd/netns.h | 1 +
> fs/locks.c | 1 +
> fs/namei.c | 1 +
> fs/nfs/nfs4_fs.h | 1 +
> fs/nfs_common/grace.c | 1 +
> fs/nfsd/netns.h | 1 +
> fs/ocfs2/locks.c | 1 +
> fs/ocfs2/stack_user.c | 1 +
Seems it misses the related changes in:
fs/ocfs2/stackglue.c
Thanks,
Joseph
> fs/open.c | 1 +
> fs/orangefs/file.c | 1 +
> fs/proc/fd.c | 1 +
> fs/utimes.c | 1 +
> fs/xattr.c | 1 +
> fs/xfs/xfs_buf.h | 1 +
> fs/xfs/xfs_file.c | 1 +
> fs/xfs/xfs_inode.c | 1 +
> include/linux/filelock.h | 428 ++++++++++++++++++++++++++++++++++++++
> include/linux/fs.h | 421 -------------------------------------
> include/linux/lockd/xdr.h | 1 +
> 38 files changed, 464 insertions(+), 421 deletions(-)
> create mode 100644 include/linux/filelock.h
>
> Unless anyone has objections, I'll plan to merge this in via the file
> locking tree for v6.3. I'd appreciate Acked-bys or Reviewed-bys from
> maintainers, however.
>
next prev parent reply other threads:[~2022-11-22 1:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 20:59 [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file Jeff Layton
2022-11-21 1:26 ` Xiubo Li
2022-11-22 3:44 ` Matthew Wilcox
2022-11-21 7:59 ` Christoph Hellwig
2022-11-21 9:19 ` Christian Brauner
2022-11-21 14:40 ` Chuck Lever III
2022-11-21 15:31 ` David Howells
2022-11-21 16:21 ` Steve French
2022-11-21 16:53 ` Darrick J. Wong
2022-11-21 17:16 ` Jeff Layton
2022-11-21 17:27 ` Darrick J. Wong
2022-11-21 19:06 ` Jeff Layton
2022-11-22 1:51 ` Joseph Qi [this message]
2022-11-22 12:20 ` Jeff Layton
2022-11-22 13:54 ` Joseph Qi
2022-11-22 3:51 ` Matthew Wilcox
2022-11-22 6:06 ` Christoph Hellwig
2022-11-22 11:13 ` Jeff Layton
2022-11-25 3:34 ` Al Viro
2022-11-25 3:48 ` Al Viro
2022-11-25 13:23 ` Jeff Layton
2022-11-25 16:44 ` Al Viro
2022-11-28 10:53 ` Jeff Layton
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=0c6a44ff-409e-99b2-eaa9-fd6e87a9e104@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).