syzbot

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 1793 Comm: jbd2/vda-8 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
[<ffffffff831a6bc4>] preempt_schedule+0x34/0x36 kernel/sched/core.c:6487
[<ffffffff80a3ae0e>] __blk_mq_delay_run_hw_queue+0x4f4/0x5f2 block/blk-mq.c:2046
[<ffffffff80a3b3f4>] blk_mq_run_hw_queue+0x276/0x39e block/blk-mq.c:2096
[<ffffffff80a4f122>] blk_mq_sched_insert_requests+0x1d6/0x8c2 block/blk-mq-sched.c:486
[<ffffffff80a41846>] blk_mq_flush_plug_list+0x2c6/0x992 block/blk-mq.c:2628
[<ffffffff80a18df8>] blk_flush_plug block/blk-core.c:1269 [inline]
[<ffffffff80a18df8>] blk_finish_plug block/blk-core.c:1293 [inline]
[<ffffffff80a18df8>] blk_finish_plug+0x9c/0xe6 block/blk-core.c:1290
[<ffffffff807e2542>] jbd2_journal_commit_transaction+0x29cc/0x4a38 fs/jbd2/commit.c:838
[<ffffffff807f1a08>] kjournald2+0x19e/0x614 fs/jbd2/journal.c:213
[<ffffffff800a7f58>] kthread+0x19e/0x1fa kernel/kthread.c:377
[<ffffffff80005724>] ret_from_exception+0x0/0x10
SMP: stopping secondary CPUs
Rebooting in 86400 seconds..