Linux RCU subsystem development
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: syzbot <syzbot+ae5b16688c0c675b1a1f@syzkaller.appspotmail.com>
Cc: jiangshanlai@gmail.com, josh@joshtriplett.org,
	linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com,
	paulmck@kernel.org, rcu@vger.kernel.org, rostedt@goodmis.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [rcu?] WARNING in srcu_invoke_callbacks (2)
Date: Wed, 19 Feb 2025 08:25:38 -0500	[thread overview]
Message-ID: <20250219132538.GA468969@joelnvbox> (raw)
In-Reply-To: <67b4c7af.050a0220.14d86d.000a.GAE@google.com>

On Tue, Feb 18, 2025 at 09:47:27AM -0800, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    a64dcfb451e2 Linux 6.14-rc2
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=12398f18580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c9c47badcd079906
> dashboard link: https://syzkaller.appspot.com/bug?extid=ae5b16688c0c675b1a1f
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: arm64
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/c0a862fcec77/disk-a64dcfb4.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f03793fc001b/vmlinux-a64dcfb4.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/ae71c33eae14/Image-a64dcfb4.gz.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ae5b16688c0c675b1a1f@syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 6430 at kernel/rcu/srcutree.c:1798 srcu_invoke_callbacks+0x368/0x3d8

This is weird, happens to be WARN_ON_ONCE(ready_cbs.len); in
srcu_invoke_callbacks().

Perhaps, stack corruption or the SRCU cblist's ->seglen got corrupted?

thanks,

 - Joel


  reply	other threads:[~2025-02-19 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 17:47 [syzbot] [rcu?] WARNING in srcu_invoke_callbacks (2) syzbot
2025-02-19 13:25 ` Joel Fernandes [this message]
2025-02-19 13:58   ` Paul E. McKenney
2025-02-19 15:09     ` Joel Fernandes
2025-08-06  8:24       ` Youngmin Nam

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=20250219132538.GA468969@joelnvbox \
    --to=joelagnelf@nvidia.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=syzbot+ae5b16688c0c675b1a1f@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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