kernel panic: corrupted stack end in ext4_file_read_iter

[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=163727f1700000
kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link: https://syzkaller.appspot.com/bug?extid=6fcd79580644be9f4589
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: [adilger...@dilger.ca linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]

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+6fcd79...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 5690 Comm: modprobe 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
[<ffffffff831a6c1a>] preempt_schedule_notrace+0x9c/0x19a kernel/sched/core.c:6541
[<ffffffff8010efcc>] rcu_read_unlock_sched_notrace include/linux/rcupdate.h:816 [inline]
[<ffffffff8010efcc>] trace_lock_acquire+0xd6/0x1fc include/trace/events/lock.h:13
[<ffffffff801167b6>] lock_acquire+0x28/0x6a kernel/locking/lockdep.c:5610
[<ffffffff806d38b6>] rcu_lock_acquire include/linux/rcupdate.h:268 [inline]
[<ffffffff806d38b6>] rcu_read_lock include/linux/rcupdate.h:694 [inline]
[<ffffffff806d38b6>] ext4_get_group_desc+0xbc/0x3c2 fs/ext4/balloc.c:284
[<ffffffff8071e2ba>] __ext4_get_inode_loc+0x154/0xc08 fs/ext4/inode.c:4392
[<ffffffff807240f6>] ext4_get_inode_loc+0xb2/0x138 fs/ext4/inode.c:4533
[<ffffffff80728176>] ext4_reserve_inode_write+0x76/0x164 fs/ext4/inode.c:5696
[<ffffffff80728786>] __ext4_mark_inode_dirty+0x17a/0x6bc fs/ext4/inode.c:5865
[<ffffffff8073313a>] ext4_dirty_inode+0x90/0xba fs/ext4/inode.c:5902
[<ffffffff8053eba4>] __mark_inode_dirty+0x40a/0xf04 fs/fs-writeback.c:2409
[<ffffffff8050f434>] generic_update_time fs/inode.c:1856 [inline]
[<ffffffff8050f434>] inode_update_time fs/inode.c:1869 [inline]
[<ffffffff8050f434>] touch_atime+0x656/0x67a fs/inode.c:1941
[<ffffffff8033d302>] file_accessed include/linux/fs.h:2421 [inline]
[<ffffffff8033d302>] filemap_read+0x780/0x78a mm/filemap.c:2744
[<ffffffff8033d596>] generic_file_read_iter+0x28a/0x338 mm/filemap.c:2822
[<ffffffff806fba40>] ext4_file_read_iter+0x126/0x338 fs/ext4/file.c:130
[<ffffffff804c48ba>] call_read_iter include/linux/fs.h:2068 [inline]
[<ffffffff804c48ba>] new_sync_read+0x290/0x3d8 fs/read_write.c:400
[<ffffffff804c8378>] vfs_read+0x2ce/0x324 fs/read_write.c:481
[<ffffffff804c880c>] ksys_read+0x10a/0x224 fs/read_write.c:619
[<ffffffff804c894e>] __do_sys_read fs/read_write.c:629 [inline]
[<ffffffff804c894e>] sys_read+0x28/0x36 fs/read_write.c:627
[<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.

[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/0000000000006b065005daf71902%40google.com.