From: Jeff Layton <jlayton@kernel.org>
To: Shardul Bankar <shardul.b@mpiricsoftware.com>, shardulsb08@gmail.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+099461f8558eb0a1f4f3@syzkaller.appspotmail.com,
chuck.lever@oracle.com, neil@brown.name, okorniev@redhat.com,
Dai.Ngo@oracle.com, tom@talpey.com, janak@mpiricsoftware.com
Subject: Re: [PATCH] nfsd: fix memory leak in nfsd_create_serv error paths
Date: Mon, 17 Nov 2025 10:36:34 -0500 [thread overview]
Message-ID: <f255c85df01f3e9f9d4022436f13e2ed76a8d4eb.camel@kernel.org> (raw)
In-Reply-To: <20251117121121.3557585-1-shardul.b@mpiricsoftware.com>
On Mon, 2025-11-17 at 17:41 +0530, Shardul Bankar wrote:
> When nfsd_create_serv() calls percpu_ref_init() to initialize
> nn->nfsd_net_ref, it allocates both a percpu reference counter
> and a percpu_ref_data structure (64 bytes). However, if the
> function fails later due to svc_create_pooled() returning NULL
> or svc_bind() returning an error, these allocations are not
> cleaned up, resulting in a memory leak.
>
> The leak manifests as:
> - Unreferenced percpu allocation (8 bytes per CPU)
> - Unreferenced percpu_ref_data structure (64 bytes)
>
> Fix this by adding percpu_ref_exit() calls in both error paths
> to properly clean up the percpu_ref_init() allocations.
>
> This patch fixes the percpu_ref leak in nfsd_create_serv() seen
> as an auxiliary leak in syzbot report 099461f8558eb0a1f4f3; the
> prepare_creds() and vsock-related leaks in the same report
> remain to be addressed separately.
>
> Reported-by: syzbot+099461f8558eb0a1f4f3@syzkaller.appspotmail.com
> Link: https://syzkaller.appspot.com/bug?extid=099461f8558eb0a1f4f3
> Fixes: 47e988147f40 ("nfsd: add nfsd_serv_try_get and nfsd_serv_put")
> Signed-off-by: Shardul Bankar <shardul.b@mpiricsoftware.com>
> ---
> fs/nfsd/nfssvc.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index 7057ddd7a0a8..32cc03a7e7be 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -633,12 +633,15 @@ int nfsd_create_serv(struct net *net)
> serv = svc_create_pooled(nfsd_programs, ARRAY_SIZE(nfsd_programs),
> &nn->nfsd_svcstats,
> nfsd_max_blksize, nfsd);
> - if (serv == NULL)
> + if (serv == NULL) {
> + percpu_ref_exit(&nn->nfsd_net_ref);
> return -ENOMEM;
> + }
>
> error = svc_bind(serv, net);
> if (error < 0) {
> svc_destroy(&serv);
> + percpu_ref_exit(&nn->nfsd_net_ref);
> return error;
> }
> spin_lock(&nfsd_notifier_lock);
Nice catch!
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-11-17 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:11 Shardul Bankar
2025-11-17 15:36 ` Jeff Layton [this message]
2025-11-17 16:15 ` 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=f255c85df01f3e9f9d4022436f13e2ed76a8d4eb.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=janak@mpiricsoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=shardul.b@mpiricsoftware.com \
--cc=shardulsb08@gmail.com \
--cc=syzbot+099461f8558eb0a1f4f3@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®