syzbot


kernel panic: stack is corrupted in inode_wait_for_writeback

Status: upstream: reported syz repro on 2024/09/15 10:56
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+7f4669fadc9ccd4f2438@syzkaller.appspotmail.com
First crash: 97d, last: 36d
Bug presence (2)
Date Name Commit Repro Result
2024/09/15 linux-5.15.y (ToT) 3a5928702e71 C [report] BUG: unable to handle kernel paging request in write_inode_now
2024/09/15 upstream (ToT) d42f7708e27c C Didn't crash
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/11/28 17:46 21m retest repro linux-5.15.y report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2024/12/08 01:28 18m fix candidate upstream error job log
2024/09/17 10:53 17m fix candidate upstream error job log

Sample crash report:
ntfs3: loop4: Mark volume as dirty due to NTFS errors
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: inode_wait_for_writeback+0x280/0x280
CPU: 0 PID: 4228 Comm: syz.4.252 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 panic+0x318/0x860 kernel/panic.c:309
 __stack_chk_fail+0x10/0x10 kernel/panic.c:761
 inode_wait_for_writeback+0x280/0x280
 evict+0x4fd/0x930 fs/inode.c:619
 ntfs_fill_super+0x3b43/0x4340 fs/ntfs3/super.c:1185
 get_tree_bdev+0x3fe/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1528
 do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
 do_mount fs/namespace.c:3348 [inline]
 __do_sys_mount fs/namespace.c:3556 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f04c6bc669a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f04c5e44e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f04c5e44ef0 RCX: 00007f04c6bc669a
RDX: 0000000020000100 RSI: 0000000020000380 RDI: 00007f04c5e44eb0
RBP: 0000000020000100 R08: 00007f04c5e44ef0 R09: 0000000000010406
R10: 0000000000010406 R11: 0000000000000246 R12: 0000000020000380
R13: 00007f04c5e44eb0 R14: 000000000001f865 R15: 0000000020000240
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/15 10:56 linux-5.15.y 3a5928702e71 08d8a733 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan kernel panic: stack is corrupted in inode_wait_for_writeback
2024/11/14 16:44 linux-5.15.y d98fd109f827 a8c99394 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan kernel panic: stack is corrupted in inode_wait_for_writeback
2024/10/09 22:20 linux-5.15.y 3a5928702e71 56fb2cb7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan kernel panic: stack is corrupted in inode_wait_for_writeback
2024/09/28 06:42 linux-5.15.y 3a5928702e71 440b26ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan kernel panic: stack is corrupted in inode_wait_for_writeback
* Struck through repros no longer work on HEAD.