From: Al Viro <viro@zeniv.linux.org.uk>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] filelock: move file locking definitions to separate header file
Date: Fri, 25 Nov 2022 03:48:14 +0000 [thread overview]
Message-ID: <Y4A6/ozhUncxbimi@ZenIV> (raw)
In-Reply-To: <20221120210004.381842-1-jlayton@kernel.org>
On Sun, Nov 20, 2022 at 03:59:57PM -0500, Jeff Layton wrote:
> --- /dev/null
> +++ b/include/linux/filelock.h
> @@ -0,0 +1,428 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef _LINUX_FILELOCK_H
> +#define _LINUX_FILELOCK_H
> +
> +#include <linux/list.h>
> +#include <linux/nfs_fs_i.h>
Umm... I'd add a comment along the lines of "struct file_lock has
a BS union by fs type; NFS side of things needs nfs_fs_i.h"
> +struct lock_manager_operations {
> + void *lm_mod_owner;
> + fl_owner_t (*lm_get_owner)(fl_owner_t);
Probably take fl_owner_t to some more neutral header...
> +#define locks_inode(f) file_inode(f)
Why do we still have that one, anyway? Separate patch, obviously,
but I would take Occam's Razor to that entity...
> +struct files_struct;
> +extern void show_fd_locks(struct seq_file *f,
> + struct file *filp, struct files_struct *files);
If anything, that would be better off as fl_owner_t... Again, a separate
patch.
next prev parent reply other threads:[~2022-11-25 3:48 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
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 [this message]
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=Y4A6/ozhUncxbimi@ZenIV \
--to=viro@zeniv.linux.org.uk \
/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).