From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@lst.de>,
Chuck Lever <chuck.lever@oracle.com>,
Amir Goldstein <amir73il@gmail.com>
Cc: 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
Subject: Re: [PATCH 4/4] exportfs,nfsd: rework checking for layout-based block device access support
Date: Mon, 13 Apr 2026 15:28:20 -0700 [thread overview]
Message-ID: <70a0192e20bc9d7672862802d16f39ed1f522893.camel@kernel.org> (raw)
In-Reply-To: <20260401144059.160746-5-hch@lst.de>
On Wed, 2026-04-01 at 16:40 +0200, Christoph Hellwig wrote:
> Currently NFSD hard codes checking support for block-style layouts.
> Lift the checks into a file system-helper and provide a exportfs-level
> helper to implement the typical checks.
>
> This prepares for supporting block layout export of multiple devices
> per file system.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> ---
> fs/nfsd/export.c | 3 +-
> fs/nfsd/nfs4layouts.c | 26 +++++------------
> fs/xfs/xfs_pnfs.c | 13 +++++++++
> include/linux/exportfs_block.h | 52 +++++++++++++++++++++++++++++++++-
> 4 files changed, 73 insertions(+), 21 deletions(-)
>
> diff --git a/fs/nfsd/export.c b/fs/nfsd/export.c
> index 8e8a76a44ff0..e20298f9212f 100644
> --- a/fs/nfsd/export.c
> +++ b/fs/nfsd/export.c
> @@ -735,7 +735,8 @@ static int svc_export_parse(struct cache_detail *cd, char *mesg, int mlen)
> goto out4;
> err = 0;
>
> - nfsd4_setup_layout_type(&exp);
> + if (exp.ex_flags & NFSEXP_PNFS)
> + nfsd4_setup_layout_type(&exp);
> }
>
There is a (minor) problem with this patch. There is a second call to
nfsd4_setup_layout_type() in Chuck's nfsd-next branch, in
nfsd_nl_parse_one_export(). It needs to be gated on this flag now, or
we end up enabling pnfs unconditionally.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-04-13 22:28 UTC|newest]
Thread overview: 14+ 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 [this message]
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-02 21:09 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 15:33 cleanup block-style layouts exports Christoph Hellwig
2026-03-31 15:33 ` [PATCH 4/4] exportfs,nfsd: rework checking for layout-based block device access support Christoph Hellwig
2026-03-31 17:52 ` Jeff Layton
2026-03-31 18:00 ` 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=70a0192e20bc9d7672862802d16f39ed1f522893.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=amir73il@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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