From: Petr Vorel <pvorel@suse.cz>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: NeilBrown <neilb@suse.de>, Jeff Layton <jlayton@kernel.org>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: don't create nfsv4recoverydir in nfsdfs when not used.
Date: Wed, 17 Apr 2024 20:34:21 +0200 [thread overview]
Message-ID: <20240417183421.GC35911@pevik> (raw)
In-Reply-To: <Zh/4pd4stFgjV7gp@tissot.1015granger.net>
> On Wed, Apr 17, 2024 at 07:25:16AM +0200, Petr Vorel wrote:
> > Hi Neil, all,
> > > When CONFIG_NFSD_LEGACY_CLIENT_TRACKING is not set, the virtual file
> > > /proc/fs/nfsd/nfsv4recoverydir
> > > is created but responds EINVAL to any access.
> > > This is not useful, is somewhat surprising, and it causes ltp to
> > > complain.
> > > The only known user of this file is in nfs-utils, which handles
> > > non-existence and read-failure equally well. So there is nothing to
> > > gain from leaving the file present but inaccessible.
> > > So this patch removes the file when its content is not available - i.e.
> > > when that config option is not selected.
> > > Also remove the #ifdef which hides some of the enum values when
> > > CONFIG_NFSD_V$ not selection. simple_fill_super() quietly ignores array
> > > entries that are not present, so having slots in the array that don't
> > > get used is perfectly acceptable. So there is no value in this #ifdef.
> > > Reported-by: Petr Vorel <pvorel@suse.cz>
> > > Reviewed-by: Jeff Layton <jlayton@kernel.org>
> > > Fixes: 74fd48739d04 ("nfsd: new Kconfig option for legacy client tracking")
> > > Signed-off-by: NeilBrown <neilb@suse.de>
> > > ---
> > > fs/nfsd/nfsctl.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> > > index 93c87587e646..340c5d61f199 100644
> > > --- a/fs/nfsd/nfsctl.c
> > > +++ b/fs/nfsd/nfsctl.c
> > > @@ -48,12 +48,10 @@ enum {
> > > NFSD_MaxBlkSize,
> > > NFSD_MaxConnections,
> > > NFSD_Filecache,
> > > -#ifdef CONFIG_NFSD_V4
> > > NFSD_Leasetime,
> > > NFSD_Gracetime,
> > > NFSD_RecoveryDir,
> > > NFSD_V4EndGrace,
> > > -#endif
> > > NFSD_MaxReserved
> > > };
> > > @@ -1360,7 +1358,9 @@ static int nfsd_fill_super(struct super_block *sb, struct fs_context *fc)
> > > #ifdef CONFIG_NFSD_V4
> > > [NFSD_Leasetime] = {"nfsv4leasetime", &transaction_ops, S_IWUSR|S_IRUSR},
> > > [NFSD_Gracetime] = {"nfsv4gracetime", &transaction_ops, S_IWUSR|S_IRUSR},
> > > +#ifdef CONFIG_NFSD_LEGACY_CLIENT_TRACKING
> > > [NFSD_RecoveryDir] = {"nfsv4recoverydir", &transaction_ops, S_IWUSR|S_IRUSR},
> > > +#endif
> > LGTM.
> > Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > Kind regards,
> > Petr
> > > [NFSD_V4EndGrace] = {"v4_end_grace", &transaction_ops, S_IWUSR|S_IRUGO},
> > > #endif
> > > /* last one */ {""}
> Thanks to you both! Applied to nfsd-next (for v6.10), unless you'd
> like this to go in sooner.
Also thanks to all for a very quick fix.
Kind regards,
Petr
prev parent reply other threads:[~2024-04-17 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 21:23 [PATCH] nfsd: don't create nfsv4recoverydir in nfsdfs when not used NeilBrown
2024-04-17 5:25 ` Petr Vorel
2024-04-17 16:28 ` Chuck Lever
2024-04-17 18:33 ` Petr Vorel
2024-04-17 18:34 ` Petr Vorel [this message]
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=20240417183421.GC35911@pevik \
--to=pvorel@suse.cz \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).