kernel panic: corrupted stack end in toggle_allocation_gate

[syzbot]

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=13ea371cf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link: https://syzkaller.appspot.com/bug?extid=8d56d2e4b913bbf7586f
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 ar...@kernel.org jba...@akamai.com jpoi...@redhat.com linux-...@vger.kernel.org linux...@lists.infradead.org pal...@dabbelt.com paul.w...@sifive.com pet...@infradead.org ros...@goodmis.org]

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+8d56d2...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 49 Comm: kworker/u4:4 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0
Hardware name: riscv-virtio,qemu (DT)
Workqueue: events_unbound toggle_allocation_gate
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
[<ffffffff831a688a>] schedule_debug kernel/sched/core.c:5541 [inline]
[<ffffffff831a688a>] schedule+0x0/0x14c kernel/sched/core.c:6187
[<ffffffff831a6b00>] preempt_schedule_common+0x4e/0xde kernel/sched/core.c:6462
[<ffffffff831a6bc4>] preempt_schedule+0x34/0x36 kernel/sched/core.c:6487
[<ffffffff831a9556>] __mutex_lock_common kernel/locking/mutex.c:608 [inline]
[<ffffffff831a9556>] __mutex_lock+0x7c6/0xade kernel/locking/mutex.c:733
[<ffffffff831a9882>] mutex_lock_nested+0x14/0x1c kernel/locking/mutex.c:785
[<ffffffff80010e30>] arch_jump_label_transform+0xcc/0x1e2 arch/riscv/kernel/jump_label.c:38
[<ffffffff803265aa>] __jump_label_update+0xfe/0x230 kernel/jump_label.c:437
[<ffffffff80326834>] jump_label_update+0x158/0x2b6 kernel/jump_label.c:830
[<ffffffff80326ae8>] static_key_enable_cpuslocked+0x156/0x19c kernel/jump_label.c:177
[<ffffffff80326b50>] static_key_enable+0x22/0x34 kernel/jump_label.c:190
[<ffffffff804777e8>] toggle_allocation_gate mm/kfence/core.c:734 [inline]
[<ffffffff804777e8>] toggle_allocation_gate+0x118/0x374 mm/kfence/core.c:726
[<ffffffff80093b44>] process_one_work+0x654/0xffe kernel/workqueue.c:2307
[<ffffffff8009484e>] worker_thread+0x360/0x8fa kernel/workqueue.c:2454
[<ffffffff800a7f58>] kthread+0x19e/0x1fa kernel/kthread.c:377
[<ffffffff80005724>] ret_from_exception+0x0/0x10
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.