From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>,
misanjum@linux.ibm.com, NeilBrown <neilb@ownmail.net>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v1 2/2] NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd
Date: Fri, 20 Feb 2026 10:52:21 -0500 [thread overview]
Message-ID: <2fa166bf4183cbc049350dc892eeb6656d9ed081.camel@kernel.org> (raw)
In-Reply-To: <20260219215017.1769-3-cel@kernel.org>
On Thu, 2026-02-19 at 16:50 -0500, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> The /proc/fs/nfs/exports proc entry is created at module init
> and persists for the module's lifetime. exports_proc_open()
> captures the caller's current network namespace and stores
> its svc_export_cache in seq->private, but takes no reference
> on the namespace. If the namespace is subsequently torn down
> (e.g. container destruction after the opener does setns() to a
> different namespace), nfsd_net_exit() calls nfsd_export_shutdown()
> which frees the cache. Subsequent reads on the still-open fd
> dereference the freed cache_detail, walking a freed hash table.
>
> Hold a reference on the struct net for the lifetime of the open
> file descriptor. This prevents nfsd_net_exit() from running --
> and thus prevents nfsd_export_shutdown() from freeing the cache
> -- while any exports fd is open. cache_detail already stores
> its net pointer (cd->net, set by cache_create_net()), so
> exports_release() can retrieve it without additional per-file
> storage.
>
> Reported-by: Misbah Anjum N <misanjum@linux.ibm.com>
> Closes: https://lore.kernel.org/linux-nfs/dcd371d3a95815a84ba7de52cef447b8@linux.ibm.com/
> Fixes: 96d851c4d28d ("nfsd: use proper net while reading "exports" file")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> fs/nfsd/nfsctl.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> index 4166f59908f4..3d5a676e1d14 100644
> --- a/fs/nfsd/nfsctl.c
> +++ b/fs/nfsd/nfsctl.c
> @@ -149,9 +149,19 @@ static int exports_net_open(struct net *net, struct file *file)
>
> seq = file->private_data;
> seq->private = nn->svc_export_cache;
> + get_net(net);
> return 0;
> }
>
> +static int exports_release(struct inode *inode, struct file *file)
> +{
> + struct seq_file *seq = file->private_data;
> + struct cache_detail *cd = seq->private;
> +
> + put_net(cd->net);
> + return seq_release(inode, file);
> +}
> +
> static int exports_nfsd_open(struct inode *inode, struct file *file)
> {
> return exports_net_open(inode->i_sb->s_fs_info, file);
> @@ -161,7 +171,7 @@ static const struct file_operations exports_nfsd_operations = {
> .open = exports_nfsd_open,
> .read = seq_read,
> .llseek = seq_lseek,
> - .release = seq_release,
> + .release = exports_release,
> };
>
> static int export_features_show(struct seq_file *m, void *v)
> @@ -1376,7 +1386,7 @@ static const struct proc_ops exports_proc_ops = {
> .proc_open = exports_proc_open,
> .proc_read = seq_read,
> .proc_lseek = seq_lseek,
> - .proc_release = seq_release,
> + .proc_release = exports_release,
> };
>
> static int create_proc_exports_entry(void)
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-02-20 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 21:50 [PATCH v1 0/2] Address UAF in sunrpc cache show callbacks Chuck Lever
2026-02-19 21:50 ` [PATCH v1 1/2] NFSD: Defer sub-object cleanup in export put callbacks Chuck Lever
2026-02-20 15:50 ` Jeff Layton
2026-02-25 18:29 ` Olga Kornievskaia
2026-02-25 18:53 ` Chuck Lever
2026-02-19 21:50 ` [PATCH v1 2/2] NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd Chuck Lever
2026-02-20 15:52 ` Jeff Layton [this message]
2026-02-25 18:29 ` Olga Kornievskaia
2026-02-21 22:57 ` [PATCH v1 0/2] Address UAF in sunrpc cache show callbacks NeilBrown
2026-02-22 15:41 ` 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=2fa166bf4183cbc049350dc892eeb6656d9ed081.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=misanjum@linux.ibm.com \
--cc=neilb@ownmail.net \
--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