kernel panic: corrupted stack end in kjournald2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c80ee64a8020 riscv: alternative only works on !XIP_KERNEL
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=14bd8e55700000
kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link: https://syzkaller.appspot.com/bug?extid=71562988aeb2b2d32767
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: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.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+715629...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 1794 Comm: jbd2/vda-8 Not tainted 5.17.0-rc1-syzkaller-00001-gc80ee64a8020 #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff8000a228>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113
[<ffffffff83166884>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119
[<ffffffff83175672>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff83175672>] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106
[<ffffffff831756fa>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff83166f60>] panic+0x24a/0x634 kernel/panic.c:233
[<ffffffff831a6842>] schedule_debug kernel/sched/core.c:5541 [inline]
[<ffffffff831a6842>] schedule+0x0/0x14c kernel/sched/core.c:6187
[<ffffffff831a6ab8>] preempt_schedule_common+0x4e/0xde kernel/sched/core.c:6462
[<ffffffff831a6b7c>] preempt_schedule+0x34/0x36 kernel/sched/core.c:6487
[<ffffffff80a3adc6>] __blk_mq_delay_run_hw_queue+0x4f4/0x5f2 block/blk-mq.c:2046
[<ffffffff80a3b3ac>] blk_mq_run_hw_queue+0x276/0x39e block/blk-mq.c:2096
[<ffffffff80a4f0da>] blk_mq_sched_insert_requests+0x1d6/0x8c2 block/blk-mq-sched.c:486
[<ffffffff80a417fe>] blk_mq_flush_plug_list+0x2c6/0x992 block/blk-mq.c:2628
[<ffffffff80a18db0>] blk_flush_plug block/blk-core.c:1269 [inline]
[<ffffffff80a18db0>] blk_finish_plug block/blk-core.c:1293 [inline]
[<ffffffff80a18db0>] blk_finish_plug+0x9c/0xe6 block/blk-core.c:1290
[<ffffffff807e24fa>] jbd2_journal_commit_transaction+0x29cc/0x4a38 fs/jbd2/commit.c:838
[<ffffffff807f19c0>] kjournald2+0x19e/0x614 fs/jbd2/journal.c:213
[<ffffffff800a7f10>] 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.

[Dmitry Vyukov]

#syz dup: kernel panic: corrupted stack end in inet_rtm_newaddr

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/000000000000678adc05daf71989%40google.com.