All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jeff Layton <jlayton@kernel.org>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	David Howells <dhowells@redhat.com>,
	Marc Dionne <marc.dionne@auristor.com>,
	Xiubo Li <xiubli@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
	Steve French <sfrench@samba.org>, Paulo Alcantara <pc@cjr.nz>,
	Ronnie Sahlberg <lsahlber@redhat.com>,
	Shyam Prasad N <sprasad@microsoft.com>,
	Tom Talpey <tom@talpey.com>,
	Christine Caulfield <ccaulfie@redhat.com>,
	David Teigland <teigland@redhat.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Bob Peterson <rpeterso@redhat.com>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna@kernel.org>, Mark Fasheh <mark@fasheh.com>,
	Joel Becker <jlbec@evilplan.org>,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	Mike Marshall <hubcap@omnibond.com>,
	Martin Brandenburg <martin@omnibond.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	hch@lst.de, linux-kernel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net,
	linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	ceph-devel@vger.kernel.org, linux-cifs@vger.kernel.org,
	samba-technical@lists.samba.org, cluster-devel@redhat.com,
	linux-nfs@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	devel@lists.orangefs.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] filelock: move file locking definitions to separate header file
Date: Fri, 25 Nov 2022 03:34:14 +0000	[thread overview]
Message-ID: <Y4A3tmISFIR7ERfE@ZenIV> (raw)
In-Reply-To: <Y3xHQwM3UiD/SK0K@casper.infradead.org>

On Tue, Nov 22, 2022 at 03:51:31AM +0000, Matthew Wilcox wrote:
> On Sun, Nov 20, 2022 at 03:59:57PM -0500, Jeff Layton wrote:
> > 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.
> 
> I'm in favour of this in general, but I think there's a few implicit
> includes.  Can you create a test.c that only #include
> <linnux/filelock.h> and see if there's anything missing?
> 
> > +	wait_queue_head_t fl_wait;
> > +	struct file *fl_file;
> 
> These two seem undefined at this point.
> 
> > +	struct fasync_struct *	fl_fasync; /* for lease break notifications */
> 
> Likewise.

#include <linux/wait.h>

struct file;
struct fasync_struct;



WARNING: multiple messages have this Message-ID (diff)
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:34:14 +0000	[thread overview]
Message-ID: <Y4A3tmISFIR7ERfE@ZenIV> (raw)
In-Reply-To: <Y3xHQwM3UiD/SK0K@casper.infradead.org>

On Tue, Nov 22, 2022 at 03:51:31AM +0000, Matthew Wilcox wrote:
> On Sun, Nov 20, 2022 at 03:59:57PM -0500, Jeff Layton wrote:
> > 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.
> 
> I'm in favour of this in general, but I think there's a few implicit
> includes.  Can you create a test.c that only #include
> <linnux/filelock.h> and see if there's anything missing?
> 
> > +	wait_queue_head_t fl_wait;
> > +	struct file *fl_file;
> 
> These two seem undefined at this point.
> 
> > +	struct fasync_struct *	fl_fasync; /* for lease break notifications */
> 
> Likewise.

#include <linux/wait.h>

struct file;
struct fasync_struct;



WARNING: multiple messages have this Message-ID (diff)
From: Al Viro via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Martin Brandenburg <martin@omnibond.com>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	David Howells <dhowells@redhat.com>,
	Marc Dionne <marc.dionne@auristor.com>,
	samba-technical@lists.samba.org, linux-xfs@vger.kernel.org,
	Mike Marshall <hubcap@omnibond.com>,
	linux-cifs@vger.kernel.org,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	linux-afs@lists.infradead.org, cluster-devel@redhat.com,
	Christine Caulfield <ccaulfie@redhat.com>,
	v9fs-developer@lists.sourceforge.net,
	Ilya Dryomov <idryomov@gmail.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	devel@lists.orangefs.org, Shyam Prasad N <sprasad@microsoft.com>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Tom Talpey <tom@talpey.com>,
	linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
	Xiubo Li <xiubli@redhat.com>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	linux-nfs@vger.kernel.org, Paulo Alcantara <pc@cjr.nz>,
	Jeff Layton <jlayton@kernel.org>,
	linux-kernel@vger.kernel.org,
	Ronnie Sahlberg <lsahlber@redhat.com>,
	Steve French <sfrench@samba.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Anna Schumaker <anna@kernel.org>,
	Bob Peterson <rpeterso@redhat.com>,
	ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH] filelock: move file locking definitions to separate header file
Date: Fri, 25 Nov 2022 03:34:14 +0000	[thread overview]
Message-ID: <Y4A3tmISFIR7ERfE@ZenIV> (raw)
In-Reply-To: <Y3xHQwM3UiD/SK0K@casper.infradead.org>

On Tue, Nov 22, 2022 at 03:51:31AM +0000, Matthew Wilcox wrote:
> On Sun, Nov 20, 2022 at 03:59:57PM -0500, Jeff Layton wrote:
> > 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.
> 
> I'm in favour of this in general, but I think there's a few implicit
> includes.  Can you create a test.c that only #include
> <linnux/filelock.h> and see if there's anything missing?
> 
> > +	wait_queue_head_t fl_wait;
> > +	struct file *fl_file;
> 
> These two seem undefined at this point.
> 
> > +	struct fasync_struct *	fl_fasync; /* for lease break notifications */
> 
> Likewise.

#include <linux/wait.h>

struct file;
struct fasync_struct;



_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

  parent reply	other threads:[~2022-11-25  3:35 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 20:59 [PATCH] filelock: move file locking definitions to separate header file Jeff Layton
2022-11-20 20:59 ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-20 20:59 ` [Cluster-devel] " Jeff Layton
2022-11-21  1:26 ` Xiubo Li
2022-11-21  1:26   ` [Ocfs2-devel] " Xiubo Li via Ocfs2-devel
2022-11-21  1:26   ` [Cluster-devel] " Xiubo Li
2022-11-22  3:44   ` Matthew Wilcox
2022-11-22  3:44     ` [Ocfs2-devel] " Matthew Wilcox via Ocfs2-devel
2022-11-22  3:44     ` [Cluster-devel] " Matthew Wilcox
2022-11-21  7:59 ` Christoph Hellwig
2022-11-21  7:59   ` [Ocfs2-devel] " Christoph Hellwig via Ocfs2-devel
2022-11-21  7:59   ` [Cluster-devel] " Christoph Hellwig
2022-11-21  9:19 ` Christian Brauner
2022-11-21  9:19   ` [Ocfs2-devel] " Christian Brauner via Ocfs2-devel
2022-11-21  9:19   ` [Cluster-devel] " Christian Brauner
2022-11-21 14:40 ` Chuck Lever III
2022-11-21 14:40   ` [Ocfs2-devel] " Chuck Lever III via Ocfs2-devel
2022-11-21 14:40   ` [Cluster-devel] " Chuck Lever III
2022-11-21 15:31 ` David Howells
2022-11-21 15:31   ` [Ocfs2-devel] " David Howells via Ocfs2-devel
2022-11-21 15:31   ` [Cluster-devel] " David Howells
2022-11-21 16:21 ` Steve French
2022-11-21 16:21   ` [Ocfs2-devel] " Steve French via Ocfs2-devel
2022-11-21 16:21   ` [Cluster-devel] " Steve French
2022-11-21 16:53 ` Darrick J. Wong
2022-11-21 16:53   ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel
2022-11-21 16:53   ` [Cluster-devel] " Darrick J. Wong
2022-11-21 17:16   ` Jeff Layton
2022-11-21 17:16     ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-21 17:16     ` [Cluster-devel] " Jeff Layton
2022-11-21 17:27     ` Darrick J. Wong
2022-11-21 17:27       ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel
2022-11-21 17:27       ` [Cluster-devel] " Darrick J. Wong
2022-11-21 19:06       ` Jeff Layton
2022-11-21 19:06         ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-21 19:06         ` [Cluster-devel] " Jeff Layton
2022-11-22  1:51 ` Joseph Qi
2022-11-22  1:51   ` [Ocfs2-devel] " Joseph Qi via Ocfs2-devel
2022-11-22  1:51   ` [Cluster-devel] " Joseph Qi
2022-11-22 12:20   ` Jeff Layton
2022-11-22 12:20     ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-22 12:20     ` [Cluster-devel] " Jeff Layton
2022-11-22 13:54     ` Joseph Qi
2022-11-22 13:54       ` [Ocfs2-devel] " Joseph Qi via Ocfs2-devel
2022-11-22 13:54       ` [Cluster-devel] " Joseph Qi
2022-11-22  3:51 ` Matthew Wilcox
2022-11-22  3:51   ` [Ocfs2-devel] " Matthew Wilcox via Ocfs2-devel
2022-11-22  3:51   ` [Cluster-devel] " Matthew Wilcox
2022-11-22  6:06   ` Christoph Hellwig
2022-11-22  6:06     ` [Ocfs2-devel] " Christoph Hellwig via Ocfs2-devel
2022-11-22  6:06     ` [Cluster-devel] " Christoph Hellwig
2022-11-22 11:13   ` Jeff Layton
2022-11-22 11:13     ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-22 11:13     ` [Cluster-devel] " Jeff Layton
2022-11-25  3:34   ` Al Viro [this message]
2022-11-25  3:34     ` [Ocfs2-devel] " Al Viro via Ocfs2-devel
2022-11-25  3:34     ` [Cluster-devel] " Al Viro
2022-11-25  3:48 ` Al Viro
2022-11-25  3:48   ` [Ocfs2-devel] " Al Viro via Ocfs2-devel
2022-11-25  3:48   ` [Cluster-devel] " Al Viro
2022-11-25 13:23   ` Jeff Layton
2022-11-25 13:23     ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-25 13:23     ` [Cluster-devel] " Jeff Layton
2022-11-25 16:44     ` Al Viro
2022-11-25 16:44       ` [Ocfs2-devel] " Al Viro via Ocfs2-devel
2022-11-25 16:44       ` [Cluster-devel] " Al Viro
2022-11-28 10:53       ` Jeff Layton
2022-11-28 10:53         ` [Ocfs2-devel] " Jeff Layton via Ocfs2-devel
2022-11-28 10:53         ` [Cluster-devel] " 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=Y4A3tmISFIR7ERfE@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=agruenba@redhat.com \
    --cc=anna@kernel.org \
    --cc=asmadeus@codewreck.org \
    --cc=ccaulfie@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=cluster-devel@redhat.com \
    --cc=devel@lists.orangefs.org \
    --cc=dhowells@redhat.com \
    --cc=djwong@kernel.org \
    --cc=ericvh@gmail.com \
    --cc=hch@lst.de \
    --cc=hubcap@omnibond.com \
    --cc=idryomov@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lsahlber@redhat.com \
    --cc=lucho@ionkov.net \
    --cc=marc.dionne@auristor.com \
    --cc=mark@fasheh.com \
    --cc=martin@omnibond.com \
    --cc=miklos@szeredi.hu \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=pc@cjr.nz \
    --cc=rpeterso@redhat.com \
    --cc=samba-technical@lists.samba.org \
    --cc=senozhatsky@chromium.org \
    --cc=sfrench@samba.org \
    --cc=sprasad@microsoft.com \
    --cc=teigland@redhat.com \
    --cc=tom@talpey.com \
    --cc=trond.myklebust@hammerspace.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=willy@infradead.org \
    --cc=xiubli@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.