public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@google.com>
To: cel@kernel.org
Cc: Dai.Ngo@oracle.com, chuck.lever@oracle.com, jlayton@kernel.org,
	 kuniyu@google.com, linux-nfs@vger.kernel.org,
	lorenzo@kernel.org,  neil@brown.name, okorniev@redhat.com,
	tom@talpey.com
Subject: Re: [PATCH v1 0/2] nfsd: Fix cred refcount leak.
Date: Sat, 28 Feb 2026 20:01:26 +0000	[thread overview]
Message-ID: <20260228200214.964918-1-kuniyu@google.com> (raw)
In-Reply-To: <176931125800.30355.7451399373487878151.b4-ty@oracle.com>

Hi Chuck,

From: Chuck Lever <cel@kernel.org>
Date: Sat, 24 Jan 2026 22:21:05 -0500
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> On Sat, 24 Jan 2026 04:18:39 +0000, Kuniyuki Iwashima wrote:
> > get_current_cred() is misused in nfsd_nl_listener_set_doit()
> > and nfsd_nl_threads_set_doit(), leaking the cred refcount.
> > 
> > Patch 1 & 2 fixes the leak in each function.
> > 
> > 
> > Kuniyuki Iwashima (2):
> >   nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().
> >   nfsd: Fix cred ref leak in nfsd_nl_listener_set_doit().
> > 
> > [...]
> 
> Applied to nfsd-testing, thanks!
> 
> [1/2] nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().
>       commit: c14b0c3b5966a1e2cf6a7f219c4f4b3fafeb89d0
> [2/2] nfsd: Fix cred ref leak in nfsd_nl_listener_set_doit().
>       commit: 687b9b69fcda9de606e998fd2edccb8a14406e19

While rebasing my local branch, I just noticed both patches
are not in the mainline and I couldn't find both SHA1 in your
tree.

https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/?id=c14b0c3b5966a1e2cf6a7f219c4f4b3fafeb89d0

Could you double check ?

Thanks !

  reply	other threads:[~2026-02-28 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  4:18 [PATCH v1 0/2] nfsd: Fix cred refcount leak Kuniyuki Iwashima
2026-01-24  4:18 ` [PATCH v1 1/2] nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() Kuniyuki Iwashima
2026-01-24  4:18 ` [PATCH v1 2/2] nfsd: Fix cred ref leak in nfsd_nl_listener_set_doit() Kuniyuki Iwashima
2026-01-24 15:32 ` [PATCH v1 0/2] nfsd: Fix cred refcount leak Jeff Layton
2026-01-25  3:21 ` Chuck Lever
2026-02-28 20:01   ` Kuniyuki Iwashima [this message]
2026-02-28 20:36     ` Chuck Lever
2026-02-28 20:39       ` Kuniyuki Iwashima

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=20260228200214.964918-1-kuniyu@google.com \
    --to=kuniyu@google.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lorenzo@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