[v5.15] WARNING in rcu_check_gp_start_stall (2)

0 views
Skip to first unread message

syzbot

unread,
Apr 24, 2024, 5:58:30 PM (10 days ago) Apr 24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145226a0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=63c309992cdbc358f543
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 20 at kernel/rcu/tree_stall.h:937 rcu_check_gp_start_stall+0x2c8/0x450 kernel/rcu/tree_stall.h:922
Modules linked in:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:rcu_check_gp_start_stall+0x2c8/0x450 kernel/rcu/tree_stall.h:937
Code: c7 c7 60 2c 43 91 be 04 00 00 00 e8 82 89 5e 00 b8 01 00 00 00 87 05 97 92 d7 0f 85 c0 0f 85 1c ff ff ff 48 c7 c0 c0 3a 92 8c <0f> 0b 49 39 c7 74 47 48 c7 c0 84 8e e4 8d 48 c1 e8 03 42 0f b6 04
RSP: 0018:ffffc90000da7a78 EFLAGS: 00010046
RAX: ffffffff8c923ac0 RBX: 00000000ffffcd51 RCX: ffffffff816b99be
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffffff91432c60
RBP: ffffc90000da7cb0 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000246 R15: ffffffff8c923ac0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f224000 CR3: 000000001fb44000 CR4: 00000000003526e0
Call Trace:
<TASK>
rcu_core+0x657/0x1650 kernel/rcu/tree.c:2758
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:921
smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</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 syzk...@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 all
Reply to author
Forward
0 new messages