Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
syzkaller-upstream-moderation
Conversations
About
kernel panic: stack is corrupted in sys_futex
4 views
Skip to first unread message
syzbot
unread,
Feb 7, 2023, 6:59:46 PM
2/7/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
Sign in to 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: 0966d385830d riscv: Fix auipc+jalr relocation range checks
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=10b12ce3480000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link:
https://syzkaller.appspot.com/bug?extid=ed2d630aa878147a053d
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: [
andre...@igalia.com
da...@stgolabs.net
dvh...@infradead.org
linux-...@vger.kernel.org
mi...@redhat.com
pet...@infradead.org
tg...@linutronix.de
]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+ed2d63...@syzkaller.appspotmail.com
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sys_futex+0x310/0x310 kernel/futex/syscalls.c:164
CPU: 1 PID: 3517 Comm: syz-fuzzer Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff8000a228>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113
[<ffffffff831668cc>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119
[<ffffffff831756ba>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff831756ba>] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106
[<ffffffff83175742>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff83166fa8>] panic+0x24a/0x634 kernel/panic.c:233
[<ffffffff831a1392>] warn_bogus_irq_restore+0x0/0x34 kernel/panic.c:670
[<ffffffff80195136>] sys_futex_waitv+0x0/0x46 kernel/futex/syscalls.c:164
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.
syzbot
unread,
May 4, 2023, 7:56:37 PM
5/4/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
Sign in to 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