public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, reviews@web.codeaurora.org
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
	kernel test robot <lkp@intel.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] NFSD: Avoid corruption of a referring call list
Date: Mon, 09 Jun 2025 09:37:07 -0400	[thread overview]
Message-ID: <e84e16340e203e35c917207cd0e4f10d1a09417d.camel@kernel.org> (raw)
In-Reply-To: <20250608220851.2230459-1-cel@kernel.org>

On Sun, 2025-06-08 at 18:08 -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> The new code neglects to remove a freshly-allocated RCL from the
> callback's referring call list when no matching referring call is
> found.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/r/202505171002.cE46sdj5-lkp@intel.com/
> Fixes: 4f3c8d8c9e10 ("NFSD: Implement CB_SEQUENCE referring call lists")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  fs/nfsd/nfs4callback.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> I don't recall seeing this on the mailing list. Targeting this
> one for nfsd-fixes.
> 
> 
> diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> index ccb00aa93be0..e00b2aea8da2 100644
> --- a/fs/nfsd/nfs4callback.c
> +++ b/fs/nfsd/nfs4callback.c
> @@ -1409,6 +1409,7 @@ void nfsd41_cb_referring_call(struct nfsd4_callback *cb,
>  out:
>  	if (!rcl->__nr_referring_calls) {
>  		cb->cb_nr_referring_call_list--;
> +		list_del(&rcl->__list);
>  		kfree(rcl);
>  	}
>  }

Nice catch.

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2025-06-09 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-08 22:08 [PATCH] NFSD: Avoid corruption of a referring call list Chuck Lever
2025-06-09 13:37 ` Jeff Layton [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=e84e16340e203e35c917207cd0e4f10d1a09417d.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=reviews@web.codeaurora.org \
    /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