* [PATCH 18/22] nfsd: kill stale comment about simple_fill_super() requirements [not found] <20231220051348.GY1674809@ZenIV> @ 2023-12-20 5:30 ` Al Viro 2023-12-20 14:22 ` Chuck Lever 0 siblings, 1 reply; 2+ messages in thread From: Al Viro @ 2023-12-20 5:30 UTC (permalink / raw) To: linux-fsdevel; +Cc: linux-nfs That went into the tree back in 2005; the comment used to be true for predecessor of simple_fill_super() that happened to live in nfsd; that one didn't take care to skip the array entries with NULL ->name, so it could not tolerate any gaps. That had been fixed in 2003 when nfsd_fill_super() had been abstracted into simple_fill_super(); if Neil's patch lived out of tree during that time, he probably replaced the name of function when rebasing it and didn't notice that restriction in question was no longer there. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> --- fs/nfsd/nfsctl.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c index 3e15b72f421d..26a25e40c451 100644 --- a/fs/nfsd/nfsctl.c +++ b/fs/nfsd/nfsctl.c @@ -48,10 +48,6 @@ enum { NFSD_MaxBlkSize, NFSD_MaxConnections, NFSD_Filecache, - /* - * The below MUST come last. Otherwise we leave a hole in nfsd_files[] - * with !CONFIG_NFSD_V4 and simple_fill_super() goes oops - */ #ifdef CONFIG_NFSD_V4 NFSD_Leasetime, NFSD_Gracetime, -- 2.39.2 ^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 18/22] nfsd: kill stale comment about simple_fill_super() requirements 2023-12-20 5:30 ` [PATCH 18/22] nfsd: kill stale comment about simple_fill_super() requirements Al Viro @ 2023-12-20 14:22 ` Chuck Lever 0 siblings, 0 replies; 2+ messages in thread From: Chuck Lever @ 2023-12-20 14:22 UTC (permalink / raw) To: Al Viro; +Cc: linux-fsdevel, linux-nfs On Wed, Dec 20, 2023 at 05:30:13AM +0000, Al Viro wrote: > That went into the tree back in 2005; the comment used to be true for > predecessor of simple_fill_super() that happened to live in nfsd; that one > didn't take care to skip the array entries with NULL ->name, so it could > not tolerate any gaps. That had been fixed in 2003 when nfsd_fill_super() > had been abstracted into simple_fill_super(); if Neil's patch lived out > of tree during that time, he probably replaced the name of function when > rebasing it and didn't notice that restriction in question was no longer > there. > > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Acked-by: Chuck Lever <chuck.lever@oracle.com> > --- > fs/nfsd/nfsctl.c | 4 ---- > 1 file changed, 4 deletions(-) > > diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c > index 3e15b72f421d..26a25e40c451 100644 > --- a/fs/nfsd/nfsctl.c > +++ b/fs/nfsd/nfsctl.c > @@ -48,10 +48,6 @@ enum { > NFSD_MaxBlkSize, > NFSD_MaxConnections, > NFSD_Filecache, > - /* > - * The below MUST come last. Otherwise we leave a hole in nfsd_files[] > - * with !CONFIG_NFSD_V4 and simple_fill_super() goes oops > - */ > #ifdef CONFIG_NFSD_V4 > NFSD_Leasetime, > NFSD_Gracetime, > -- > 2.39.2 > > -- Chuck Lever ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-12-20 14:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20231220051348.GY1674809@ZenIV>
2023-12-20 5:30 ` [PATCH 18/22] nfsd: kill stale comment about simple_fill_super() requirements Al Viro
2023-12-20 14:22 ` Chuck Lever
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox