From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev
Subject: Re: [jlayton:exportd-netlink 3/18] net/sunrpc/cache.c:1074 cache_release() error: dereferencing freed memory 'rq' (line 1070)
Date: Wed, 18 Mar 2026 09:30:30 -0400 [thread overview]
Message-ID: <50724bf987e3f702ebe48b9fb280fb3e4bcf0618.camel@kernel.org> (raw)
In-Reply-To: <13cd936f-0e00-4d7b-bc41-129a21cc5cad@oracle.com>
On Wed, 2026-03-18 at 09:22 -0400, Chuck Lever wrote:
> On 3/18/26 6:56 AM, Jeff Layton wrote:
> > On Wed, 2026-03-18 at 10:42 +0300, Dan Carpenter wrote:
>
> > > Looks like a bad merge.
> > >
> >
> > Thanks Dan,
> >
> > Yes it does. I based this series on top of Linus' master, and then
> > merged in Chuck's nfsd-fixes, nfsd-next and nfsd-testing branches
> > before layering these patches on top.
> >
> > It looks like the problem occurred when the nfsd-next branch was
> > merged. Both it and -fixes have the same patch.
> >
> > I'll rebase the series on top of a sane merge later today.
>
> Can you identify the patch that is the same in both branches?
> Typically, the linux-next merge will catch that kind of thing.
>
My mistake. The duplicate is in nfsd-testing, not nfsd-next:
nfsd-fixes has:
17ad31b3a43b sunrpc: fix cache_request leak in cache_release
...and nfsd-testing has:
0b88d5fcde16 sunrpc: fix cache_request leak in cache_release
Cheers,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-03-18 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 19:03 [jlayton:exportd-netlink 3/18] net/sunrpc/cache.c:1074 cache_release() error: dereferencing freed memory 'rq' (line 1070) kernel test robot
2026-03-18 7:42 ` Dan Carpenter
2026-03-18 10:56 ` Jeff Layton
2026-03-18 13:22 ` Chuck Lever
2026-03-18 13:30 ` Jeff Layton [this message]
2026-03-18 13:32 ` Chuck Lever
2026-03-18 13:33 ` Jeff Layton
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=50724bf987e3f702ebe48b9fb280fb3e4bcf0618.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dan.carpenter@linaro.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.