mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>,
	Chuck Lever <cel@kernel.org>,
	 Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>
Cc: falemi@asu.edu, linux-nfs@vger.kernel.org,
	Tom Talpey <tom@talpey.com>,  Dai Ngo <Dai.Ngo@oracle.com>,
	Olga Kornievskaia <okorniev@redhat.com>,
	NeilBrown <neil@brown.name>,
		linux-kernel@vger.kernel.org
Subject: Re: [BUG] sunrpc: rpc_pipe_msg left queued on a stack frame (nfsd cld upcall)
Date: Sat, 29 Aug 2026 07:53:45 -0400	[thread overview]
Message-ID: <f61e6c6f109aeeb37f18e96a049c702d512e1285.camel@kernel.org> (raw)
In-Reply-To: <CA+0ovCjVF58WLeen2ctdzHyWUASAAW3Y=Yjihyq0pFApYawtDg@mail.gmail.com>

On Thu, 2026-08-27 at 16:10 -0700, Farhad Alemi wrote:
> Hello Chuck Lever, Jeff Layton,
> 
> While fuzzing Linux 7.1-rc5 with syzkaller, as part of research at ASU's
> SEFCOM lab, we hit the crash below. Crash reports can be found here:
> 
>   https://github.com/farhad-alemi/public_bug_reports/tree/main/118-nfsd-cld-stack-rpc_pipe_msg-left-queued/
> 
>   ==================================================================
>   BUG: KASAN: vmalloc-out-of-bounds in
> __list_add_valid_or_report+0x6a/0x130 lib/list_debug.c:32
>   Read of size 8 at addr ffffc90007027950 by task syz.0.96/13066
>   CPU: 0 UID: 0 PID: 13066 Comm: syz.0.96 Not tainted 7.1.0-rc5 #1 PREEMPT(full)
>   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
> 1.16.3-debian-1.16.3-2 04/01/2014
>   Call Trace:
>   <TASK>
>   dump_stack_lvl+0x94/0xd0 lib/dump_stack.c:120
>   print_address_description+0x55/0x1e0 mm/kasan/report.c:378
> 
> Our reproducer.c is available upon request.
> 
> Happy to test a patch if that would help.
> 
> Regards,

We've had a lot of bugfixes go into the last couple of releases. Can
you test this against a more bleeding-edge kernel and see if it's still
a problem? Testing against Linus' master branch would be good, but if
you can pull down Chuck's nfsd-testing branch, that would be even
better.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2026-08-29 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 23:10 Farhad Alemi
2026-08-29 11:53 ` 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=f61e6c6f109aeeb37f18e96a049c702d512e1285.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=cel@kernel.org \
    --cc=falemi@asu.edu \
    --cc=farhad.alemi@berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    --cc=trondmy@kernel.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

all inboxes | Powered by JetHome®