[moderation] [mm?] kernel panic: stack is corrupted in shmem_undo_range

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5abc7438f1e9 Merge tag 'nfs-for-6.16-1' of git://git.linux..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1737a1d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a3965f6896e6e14
dashboard link: https://syzkaller.appspot.com/bug?extid=9054ef77020e22fbeb7c
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
CC: [ak...@linux-foundation.org baoli...@linux.alibaba.com hu...@google.com linux-...@vger.kernel.org linu...@kvack.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-5abc7438.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/26ddf00aebe3/vmlinux-5abc7438.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ae2036189547/bzImage-5abc7438.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9054ef...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Mark volume as dirty due to NTFS errors
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: shmem_undo_range+0x1335/0x14b0 mm/shmem.c:-1
CPU: 0 UID: 0 PID: 5323 Comm: syz.0.0 Not tainted 6.15.0-syzkaller-11796-g5abc7438f1e9 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x99/0x250 lib/dump_stack.c:120
panic+0x2db/0x790 kernel/panic.c:382
__stack_chk_fail+0x26/0x30 kernel/panic.c:869
shmem_undo_range+0x1335/0x14b0 mm/shmem.c:-1
shmem_truncate_range mm/shmem.c:1237 [inline]
shmem_evict_inode+0x272/0xa70 mm/shmem.c:1365
evict+0x504/0x9c0 fs/inode.c:810
__dentry_kill+0x209/0x660 fs/dcache.c:669
dput+0x19f/0x2b0 fs/dcache.c:911
__fput+0x68e/0xa70 fs/file_table.c:473
fput_close_sync+0x119/0x200 fs/file_table.c:570
__do_sys_close fs/open.c:1589 [inline]
__se_sys_close fs/open.c:1574 [inline]
__x64_sys_close+0x7f/0x110 fs/open.c:1574
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f054298d5ca
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 43 91 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 a3 91 02 00 8b 44 24
RSP: 002b:00007f0543802e00 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007f054298d5ca
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 0000000000000010 R08: 0000000000000000 R09: 0000000000000564
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000006
R13: 00007f0543802ef0 R14: 00007f0543802eb0 R15: 00007f0536800000
</TASK>
Kernel Offset: disabled
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

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