kernel panic: corrupted stack end in chrdev_open

[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=156a7b57880000
kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link: https://syzkaller.appspot.com/bug?extid=87902d915e826132603a
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: [da...@davemloft.net edum...@google.com krzysztof...@linaro.org ku...@kernel.org li...@zju.edu.cn linux-...@vger.kernel.org net...@vger.kernel.org pab...@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+87902d...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 3112 Comm: syz-executor.0 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
[<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
[<ffffffff800c5e5c>] preempt_schedule kernel/sched/core.c:6487 [inline]
[<ffffffff800c5e5c>] try_to_wake_up+0x47a/0x748 kernel/sched/core.c:4139
[<ffffffff800c613a>] wake_up_process+0x10/0x18 kernel/sched/core.c:4217
[<ffffffff800a6bf6>] __kthread_create_on_node+0x1e4/0x396 kernel/kthread.c:436
[<ffffffff800a6e4e>] kthread_create_on_node+0xa6/0xd8 kernel/kthread.c:513
[<ffffffff8008cff6>] init_rescuer kernel/workqueue.c:4283 [inline]
[<ffffffff8008cff6>] init_rescuer+0xa0/0x11e kernel/workqueue.c:4270
[<ffffffff8009d1fe>] alloc_workqueue+0x88c/0x92e kernel/workqueue.c:4358
[<ffffffff830d1ae0>] nci_register_device+0x198/0x612 net/nfc/nci/core.c:1220
[<ffffffff8148d5aa>] virtual_ncidev_open+0x82/0x12c drivers/nfc/virtual_ncidev.c:143
[<ffffffff80dec4aa>] misc_open+0x272/0x2c8 drivers/char/misc.c:141
[<ffffffff804d21b0>] chrdev_open+0x1d4/0x478 fs/char_dev.c:414
[<ffffffff804bed6c>] do_dentry_open+0x2a4/0x7d4 fs/open.c:824
[<ffffffff804c22ce>] vfs_open+0x52/0x5e fs/open.c:959
[<ffffffff804ecc4c>] do_open fs/namei.c:3476 [inline]
[<ffffffff804ecc4c>] path_openat+0x12b6/0x189e fs/namei.c:3609
[<ffffffff804efc60>] do_filp_open+0x10e/0x22a fs/namei.c:3636
[<ffffffff804c2a46>] do_sys_openat2+0x174/0x31e fs/open.c:1214
[<ffffffff804c3446>] do_sys_open fs/open.c:1230 [inline]
[<ffffffff804c3446>] __do_sys_openat fs/open.c:1246 [inline]
[<ffffffff804c3446>] sys_openat+0xdc/0x164 fs/open.c:1241
[<ffffffff80005716>] ret_from_syscall+0x0/0x2
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.