public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8f70859e7bdfbdc69bda@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-kernel@vger.kernel.org, mingo@redhat.com,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	x86@kernel.org
Subject: [syzbot] [kernel?] WARNING in try_check_zero
Date: Mon, 20 May 2024 10:27:22 -0700	[thread overview]
Message-ID: <00000000000098bb530618e60313@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    eb6a9339efeb Merge tag 'mm-nonmm-stable-2024-05-19-11-56' ..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12a0c2b2980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e2ea586e11acd6ec
dashboard link: https://syzkaller.appspot.com/bug?extid=8f70859e7bdfbdc69bda
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-eb6a9339.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21782c1528d1/vmlinux-eb6a9339.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c377678e8b1/bzImage-eb6a9339.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8f70859e7bdfbdc69bda@syzkaller.appspotmail.com

------------[ cut here ]------------
Mixed NMI-safe readers for srcu_struct at 0xffffc9000dac28a8.
WARNING: CPU: 3 PID: 1945 at kernel/rcu/srcutree.c:453 srcu_readers_unlock_idx kernel/rcu/srcutree.c:453 [inline]
WARNING: CPU: 3 PID: 1945 at kernel/rcu/srcutree.c:453 srcu_readers_active_idx_check kernel/rcu/srcutree.c:466 [inline]
WARNING: CPU: 3 PID: 1945 at kernel/rcu/srcutree.c:453 try_check_zero+0x3aa/0x560 kernel/rcu/srcutree.c:1078
Modules linked in:
CPU: 3 PID: 1945 Comm: kworker/3:2 Not tainted 6.9.0-syzkaller-09699-geb6a9339efeb #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: rcu_gp process_srcu
RIP: 0010:srcu_readers_unlock_idx kernel/rcu/srcutree.c:453 [inline]
RIP: 0010:srcu_readers_active_idx_check kernel/rcu/srcutree.c:466 [inline]
RIP: 0010:try_check_zero+0x3aa/0x560 kernel/rcu/srcutree.c:1078
Code: e9 8a fe ff ff 80 3d 6e 4b 57 0e 00 0f 85 47 fe ff ff c6 05 61 4b 57 0e 01 90 48 c7 c7 a0 42 2e 8b 4c 89 f6 e8 e7 8e dc ff 90 <0f> 0b 90 90 e9 26 fe ff ff 48 83 c4 48 31 c0 5b 5d 41 5c 41 5d 41
RSP: 0018:ffffc9000d44fb70 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffe8ffffd5c100 RCX: ffffffff81510229
RDX: ffff888021a14880 RSI: ffffffff81510236 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000003 R12: 000000000000001d
R13: dffffc0000000000 R14: ffffc9000dac28a8 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88802c300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002054b000 CR3: 000000001e250000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 srcu_advance_state kernel/rcu/srcutree.c:1684 [inline]
 process_srcu+0x3f9/0x1730 kernel/rcu/srcutree.c:1811
 process_one_work+0x958/0x1ad0 kernel/workqueue.c:3231
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2024-05-20 17:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00000000000098bb530618e60313@google.com \
    --to=syzbot+8f70859e7bdfbdc69bda@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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