Groups
Sign in
Groups
syzkaller-upstream-moderation
Conversations
About
Send feedback
Help
kernel panic: stack is corrupted in __schedule (3)
5 views
Skip to first unread message
syzbot
unread,
Aug 15, 2022, 5:43:24 PM
8/15/22
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=10ec89fd080000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link:
https://syzkaller.appspot.com/bug?extid=0fd8b9f031b04f34c82e
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: [
bra...@kernel.org
bri...@redhat.com
bse...@google.com
dietmar....@arm.com
juri....@redhat.com
linux-...@vger.kernel.org
mgo...@suse.de
mi...@redhat.com
pet...@infradead.org
ros...@goodmis.org
vincent...@linaro.org
vsch...@redhat.com
]
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+0fd8b9...@syzkaller.appspotmail.com
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x117a/0x118e kernel/sched/core.c:6304
CPU: 1 PID: 19 Comm: ksoftirqd/1 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
[<ffffffff831a6876>] __schedule+0x117a/0x118e kernel/sched/core.c:6304
SMP: stopping secondary CPUs
SMP: failed to stop secondary CPUs 0-1
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,
Nov 22, 2022, 10:17:35 PM
11/22/22
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