From: syzbot <syzbot+94c142d893fadc95fe49@syzkaller.appspotmail.com>
To: Henry.Wang@arm.com, bigeasy@linutronix.de,
linux-kernel@vger.kernel.org, longpeng2@huawei.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vschneid@redhat.com
Subject: [syzbot] upstream boot error: WARNING: ODEBUG bug in __do_softirq
Date: Tue, 16 Aug 2022 01:42:25 -0700 [thread overview]
Message-ID: <0000000000004b540c05e657ba2e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 69dac8e431af Merge tag 'riscv-for-linus-5.20-mw2' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12af94d3080000
kernel config: https://syzkaller.appspot.com/x/.config?x=f6bcb425ba129b87
dashboard link: https://syzkaller.appspot.com/bug?extid=94c142d893fadc95fe49
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+94c142d893fadc95fe49@syzkaller.appspotmail.com
------------[ cut here ]------------
ODEBUG: active_state not available (active state 0) object type: rcu_head hint: 0x0
WARNING: CPU: 1 PID: 21 at lib/debugobjects.c:502 debug_print_object+0x16e/0x250 lib/debugobjects.c:502
Modules linked in:
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.19.0-syzkaller-14184-g69dac8e431af #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:502
Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd e0 fe 48 8a 4c 89 ee 48 c7 c7 80 f2 48 8a e8 bf 17 39 05 <0f> 0b 83 05 45 ca dd 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:ffffc900001b7c10 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000000
RDX: ffff888011ba1d80 RSI: ffffffff8161f148 RDI: fffff52000036f74
RBP: 0000000000000001 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000100 R11: 0000000000000001 R12: ffffffff89ee2100
R13: ffffffff8a48f760 R14: 0000000000000000 R15: ffff88800000eda9
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000bc8e000 CR4: 0000000000350ee0
Call Trace:
<TASK>
debug_object_active_state lib/debugobjects.c:948 [inline]
debug_object_active_state+0x1d2/0x350 lib/debugobjects.c:911
debug_rcu_head_unqueue kernel/rcu/rcu.h:198 [inline]
rcu_do_batch kernel/rcu/tree.c:2238 [inline]
rcu_core+0x75e/0x1890 kernel/rcu/tree.c:2505
__do_softirq+0x1d3/0x9c6 kernel/softirq.c:571
run_ksoftirqd kernel/softirq.c:934 [inline]
run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926
smpboot_thread_fn+0x645/0x9c0 kernel/smpboot.c:164
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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.
reply other threads:[~2022-08-16 9:54 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=0000000000004b540c05e657ba2e@google.com \
--to=syzbot+94c142d893fadc95fe49@syzkaller.appspotmail.com \
--cc=Henry.Wang@arm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.