[v5.15] linux-5.15.y boot error: WARNING in trc_inspect_reader

0 views
Skip to first unread message

syzbot

unread,
Oct 6, 2023, 8:09:52 AM10/6/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1edcec18cfb7 Linux 5.15.134
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108d938a680000
kernel config: https://syzkaller.appspot.com/x/.config?x=48b4459c94d40a13
dashboard link: https://syzkaller.appspot.com/bug?extid=a2a68a2dca34d9cd33fb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e1026cce7395/disk-1edcec18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0a562b315d9c/vmlinux-1edcec18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5a8a2cdde6e6/bzImage-1edcec18.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 12 at kernel/rcu/tasks.h:958 trc_inspect_reader+0x183/0x250 kernel/rcu/tasks.h:991
Modules linked in:
CPU: 0 PID: 12 Comm: rcu_tasks_trace Not tainted 5.15.134-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
RIP: 0010:trc_inspect_reader+0x183/0x250 kernel/rcu/tasks.h:958
Code: 84 c0 0f 85 ca 00 00 00 41 c6 06 01 31 ed 85 ed 0f 94 c0 5b 41 5c 41 5e 41 5f 5d c3 0f 0b e9 bd fe ff ff 0f 0b e9 7c ff ff ff <0f> 0b eb aa 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 96 fe ff ff 48 89
RSP: 0000:ffffc90000d17b10 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff88813fe7802c RCX: ffffffff816a78d2
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88813fe78000
RBP: ffffc90000d17bf0 R08: dffffc0000000000 R09: fffffbfff1bc8296
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88813fe78000
R13: ffff88813fe78068 R14: ffff88813fe78000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000c68e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
try_invoke_on_locked_down_task+0x1c2/0x450 kernel/sched/core.c:4181
trc_wait_for_one_reader+0xa2/0x700 kernel/rcu/tasks.h:1015
rcu_tasks_trace_pertask kernel/rcu/tasks.h:1082 [inline]
rcu_tasks_trace_postscan+0xd1/0x190 kernel/rcu/tasks.h:1094
rcu_tasks_wait_gp+0x48a/0x9d0 kernel/rcu/tasks.h:327
rcu_tasks_kthread+0x2d7/0x640 kernel/rcu/tasks.h:226
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

syzbot

unread,
Jan 27, 2024, 6:00:21 AMJan 27
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages