kernel panic: stack is corrupted in wnd_find

4 views
Skip to first unread message

syzbot

unread,
Nov 19, 2022, 4:44:44 PM11/19/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9e4ce762f0e7 Merge branches 'for-next/acpi', 'for-next/asm..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=11358111880000
kernel config: https://syzkaller.appspot.com/x/.config?x=20ffacc1ce1c99b5
dashboard link: https://syzkaller.appspot.com/bug?extid=f030134432f6ca7d974d
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [almaz.ale...@paragon-software.com linux-...@vger.kernel.org ll...@lists.linux.dev nat...@kernel.org ndesau...@google.com nt...@lists.linux.dev tr...@redhat.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a70eb29add74/disk-9e4ce762.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/769d096516a8/vmlinux-9e4ce762.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9309615f51d5/Image-9e4ce762.gz.xz

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

loop3: detected capacity change from 0 to 8226
ntfs3: loop3: Mark volume as dirty due to NTFS errors
ntfs3: loop3: Failed to load $Extend.
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: wnd_find+0x11b4/0x1208
CPU: 0 PID: 22609 Comm: syz-executor.3 Not tainted 6.1.0-rc5-syzkaller-32254-g9e4ce762f0e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156
show_stack+0x2c/0x54 arch/arm64/kernel/stacktrace.c:163
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
panic+0x218/0x508 kernel/panic.c:274
warn_bogus_irq_restore+0x0/0x40 kernel/panic.c:703
wnd_find+0x11b4/0x1208
ntfs_look_for_free_space+0x154/0x340 fs/ntfs3/fsntfs.c:406
attr_allocate_clusters+0xc4/0x2bc fs/ntfs3/attrib.c:182
attr_set_size+0x944/0x132c fs/ntfs3/attrib.c:576
ntfs_set_size+0xe4/0x150 fs/ntfs3/inode.c:817
ntfs_extend+0xc0/0x274 fs/ntfs3/file.c:432
ntfs_file_write_iter+0x1b8/0x330 fs/ntfs3/file.c:1159
do_iter_write+0x318/0x560 fs/read_write.c:861
vfs_iter_write+0x4c/0x6c fs/read_write.c:902
iter_file_splice_write+0x2a8/0x518 fs/splice.c:686
do_splice_from fs/splice.c:764 [inline]
direct_splice_actor+0x4c/0xe0 fs/splice.c:931
splice_direct_to_actor+0x1dc/0x3e4 fs/splice.c:886
do_splice_direct+0xc4/0x14c fs/splice.c:974
do_sendfile+0x298/0x68c fs/read_write.c:1255
__do_sys_sendfile64 fs/read_write.c:1323 [inline]
__se_sys_sendfile64 fs/read_write.c:1309 [inline]
__arm64_sys_sendfile64+0xb0/0x230 fs/read_write.c:1309
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x00000,040e0108,4c017203
Memory Limit: none
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

unread,
Feb 18, 2023, 8:04:49 PM2/18/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages