Groups
Groups
Sign in
Groups
Groups
syzkaller-upstream-moderation
Conversations
About
Send feedback
Help
[riscv?] kernel panic: Kernel stack overflow
33 views
Skip to first unread message
syzbot
unread,
Jun 22, 2023, 9:08:08 AM
6/22/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: b104dbedbe61 Documentation: RISC-V: patch-acceptance: ment..
git tree: git://
git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
fixes
console output:
https://syzkaller.appspot.com/x/log.txt?x=1391d897280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=ed6592854c33eb63
dashboard link:
https://syzkaller.appspot.com/bug?extid=3f3bba96295371282a99
compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: riscv64
CC: [
a...@eecs.berkeley.edu
linux-...@vger.kernel.org
linux...@lists.infradead.org
pal...@dabbelt.com
paul.w...@sifive.com
]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable):
https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-b104dbed.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/84dc3813c212/vmlinux-b104dbed.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a760b8ab47cf/Image-b104dbed.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3f3bba...@syzkaller.appspotmail.com
s11: ff6000004050bd40 t3 : fffffffff3f3f300 t4 : ffffffff801349ac
t5 : 1fe4000000a44048 t6 : ff20000005220e98
status: 0000000000000100 badaddr: ff2000000521fff0 cause: 000000000000000f
Kernel panic - not syncing: Kernel stack overflow
CPU: 0 PID: 17066 Comm: syz-executor.1 Not tainted 6.4.0-rc1-syzkaller-00012-gb104dbedbe61 #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff8000aa96>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:121
[<ffffffff834dd8b4>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:127
[<ffffffff8351d78e>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff8351d78e>] dump_stack_lvl+0xe0/0x14c lib/dump_stack.c:106
[<ffffffff8351d816>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff834de0de>] panic+0x27c/0x662 kernel/panic.c:340
[<ffffffff8000a706>] walk_stackframe+0x0/0x2fe arch/riscv/kernel/traps.c:390
[<ffffffff8013387c>] mark_lock+0x16c/0xe1a kernel/locking/lockdep.c:4620
SMP: stopping secondary CPUs
Rebooting in 86400 seconds..
---
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 change 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,
Sep 16, 2023, 9:05:42 AM
9/16/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to syzkaller-upst...@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