From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <cel@kernel.org>, Christoph Hellwig <hch@lst.de>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>,
Amir Goldstein <amir73il@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: cleanup block-style layouts exports v2
Date: Mon, 27 Apr 2026 17:03:52 +0200 [thread overview]
Message-ID: <20260427-landhaus-leiblich-cd21a25f741f@brauner> (raw)
In-Reply-To: <fb0803567b6176715d00e7c34a3095647f66f8d0.camel@kernel.org>
On Thu, Apr 23, 2026 at 02:57:05PM -0400, Jeff Layton wrote:
> On Tue, 2026-04-21 at 14:04 +0200, Christian Brauner wrote:
> > On Fri, Apr 17, 2026 at 07:52:20AM -0700, Chuck Lever wrote:
> > >
> > > On Wed, Apr 15, 2026, at 7:34 AM, Chuck Lever wrote:
> > > > On Tue, Apr 14, 2026, at 10:29 PM, Christoph Hellwig wrote:
> > > > > On Tue, Apr 14, 2026 at 12:01:39PM +0200, Christian Brauner wrote:
> > > > > > On Fri, Apr 10, 2026 at 01:10:07PM +0200, Christoph Hellwig wrote:
> > > > > > > On Thu, Apr 09, 2026 at 03:26:09PM +0200, Christian Brauner wrote:
> > > > > > > > > Christian, are you OK if I take this series through the NFSD tree?
> > > > > > > >
> > > > > > > > Hm, I generally prefer infrastructure to go through the VFS tree.
> > > > > > > > You can get a stable branch ofc.
> > >
> > > > In this case, pNFS is the only consumer that will notice or use the
> > > > new "infrastructure" and us NFS experts are the only ones who can test
> > > > and review it properly. And, the likelihood of conflicts with patches
> > > > in nfsd-testing is high (in fact we've already had at least one). It
> > > > makes sense to me to take this series through NFSD.
> > >
> > > I see that Jeff has posted a series that modifies the fs_notify API surface
> > > to support the NFSv4 CB_NOTIFY operation. That likely counts as an
> > > infrastructure change.
> > >
> > > To meet you halfway, Christian, you could take Christoph's series and
> > > Jeff's series into a "vfs.nfsd" tree and I can base my nfsd-next branch
> > > on that for the NFSD PR 7.2. Building the NFSD PR on that should avoid
> > > merge conflicts with significant changes I have planned.
> >
> > Sounds perfect. I don't rebase branches unless there's something really
> > really gnarly to handle and I would ping you in advance if anything like
> > that were to happen.
>
> Note that there is a small difference (error-handling fix) between the
> most-recently posted CB_NOTIFY patchset and what's currently in my
> tree. You can either pick or pull the series from my tree, or I can re-
> post. Let me know which you'd prefer:
Just repost, if you would be so kind. (I wonder whether we should start
having a quiet period for new work during the mw like net has.)
next prev parent reply other threads:[~2026-04-27 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:40 cleanup block-style layouts exports v2 Christoph Hellwig
2026-04-01 14:40 ` [PATCH 1/4] nfsd/blocklayout: always ignore loca_time_modify Christoph Hellwig
2026-04-01 14:40 ` [PATCH 2/4] exportfs: split out the ops for layout-based block device access Christoph Hellwig
2026-04-01 14:40 ` [PATCH 3/4] exportfs: don't pass struct iattr to ->commit_blocks Christoph Hellwig
2026-04-01 14:40 ` [PATCH 4/4] exportfs,nfsd: rework checking for layout-based block device access support Christoph Hellwig
2026-04-13 22:28 ` Jeff Layton
2026-04-01 20:31 ` cleanup block-style layouts exports v2 Chuck Lever
2026-04-09 13:26 ` Christian Brauner
2026-04-10 11:10 ` Christoph Hellwig
2026-04-14 10:01 ` Christian Brauner
2026-04-15 5:29 ` Christoph Hellwig
2026-04-15 14:34 ` Chuck Lever
2026-04-17 14:52 ` Chuck Lever
2026-04-21 12:04 ` Christian Brauner
2026-04-23 18:57 ` Jeff Layton
2026-04-27 15:03 ` Christian Brauner [this message]
2026-04-16 9:27 ` Christian Brauner
2026-04-02 21:09 ` Chuck Lever
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=20260427-landhaus-leiblich-cd21a25f741f@brauner \
--to=brauner@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=amir73il@gmail.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=torvalds@linux-foundation.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).