syzbot

 sign-in | mailing list | source | docs
🐞 Open [1646]
≡ Subsystems
🐞 Fixed [6009]
🐞 Invalid [14804]
⬇ Missing Backports [135]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

kernel panic: stack is corrupted in writeback_single_inode

Status: auto-obsoleted due to no activity on 2024/03/04 03:09
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+84b7b87a6430a152c1f4@syzkaller.appspotmail.com
First crash: 894d, last: 611d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] kernel panic: stack is corrupted in writeback_single_inode 2 (5) 2022/09/30 14:09
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/03/04 02:58 21m retest repro upstream OK log
2024/03/04 02:36 26m retest repro upstream OK log
2024/03/04 02:36 19m retest repro upstream OK log
2024/03/04 00:20 17m retest repro upstream OK log
2024/01/26 12:27 20m retest repro upstream OK log
2023/12/24 23:50 16m retest repro upstream report log
2023/12/24 23:50 23m retest repro upstream OK log
2023/12/24 23:50 22m retest repro upstream report log
2023/12/24 23:50 16m retest repro upstream report log
2023/11/16 19:30 25m retest repro upstream report log
▶ ▼ Fix bisection attempts (7)
Created Duration User Patch Repo Result
2023/06/28 13:32 28m bisect fix upstream OK (0) job log
2023/05/28 15:19 32m bisect fix upstream OK (0) job log log
2023/04/28 13:13 1h00m bisect fix upstream OK (0) job log log
2023/03/29 12:13 59m bisect fix upstream OK (0) job log log
2023/02/27 11:40 32m bisect fix upstream OK (0) job log log
2023/01/23 13:12 53m (2) bisect fix upstream OK (0) job log log
2022/11/07 07:14 54m bisect fix upstream OK (0) job log log

Sample crash report:
ntfs3: loop5: Different NTFS' sector size (1024) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: writeback_single_inode+0x8e7/0x8f0
CPU: 1 PID: 5399 Comm: syz-executor475 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 panic+0x2d6/0x715 kernel/panic.c:274
 __stack_chk_fail+0x12/0x20 kernel/panic.c:706
 writeback_single_inode+0x8e7/0x8f0
 write_inode_now+0x1cd/0x260 fs/fs-writeback.c:2723
 iput_final fs/inode.c:1735 [inline]
 iput+0x3e6/0x760 fs/inode.c:1774
 ntfs_fill_super+0x3af3/0x42a0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f1c9ca9772a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 58 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe741f23a8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1c9ca9772a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffe741f23c0
RBP: 00007ffe741f23c0 R08: 00007ffe741f2400 R09: 00005555559df380
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffe741f2400 R14: 0000000000000215 R15: 00000000200033f8
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (33):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/05 18:06 upstream 0326074ff465 267e3bb1 .config console log report syz C [disk image] [vmlinux] [mounted in repro] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/29 20:25 upstream c3e0e1e23c70 45fd7169 .config console log report syz C [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/05 15:06 upstream 0326074ff465 267e3bb1 .config strace log report syz C [disk image] [vmlinux] [mounted in repro] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/02 15:37 upstream b357fd1c2afc feb56351 .config console log report syz [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/30 00:06 upstream c3e0e1e23c70 45fd7169 .config console log report syz [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/28 20:51 upstream 49c13ed0316d e2556bc3 .config console log report syz ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in writeback_single_inode
2022/10/07 12:22 upstream 4c86114194e6 79a59635 .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/06 09:58 upstream 2bca25eaeba6 2c6543ad .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/05 21:25 upstream 2bca25eaeba6 2c6543ad .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/05 20:02 upstream 0326074ff465 267e3bb1 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/05 17:53 upstream 0326074ff465 267e3bb1 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/04 18:43 upstream a5088ee7251e eab8f949 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in writeback_single_inode
2022/10/04 02:35 upstream 4fe89d07dcc2 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/04 02:22 upstream 4fe89d07dcc2 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/02 15:29 upstream b357fd1c2afc feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/02 12:37 upstream b357fd1c2afc feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/01 17:19 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/01 14:53 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/10/01 13:18 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/30 18:39 upstream 70575e77839f feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/30 08:34 upstream 987a926c1d8a 45fd7169 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/29 09:40 upstream 49c13ed0316d a41a2080 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/29 05:20 upstream 49c13ed0316d a41a2080 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/28 04:11 upstream 46452d3786a8 75c78242 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/27 13:18 upstream 3800a713b607 10323ddf .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/27 08:25 upstream 3800a713b607 10323ddf .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/27 05:28 upstream 3800a713b607 10323ddf .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/25 13:48 upstream 105a36f3694e 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/25 04:57 upstream 3db61221f4e8 0042f2b4 .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/24 19:53 upstream 3db61221f4e8 0042f2b4 .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/20 00:36 upstream 521a547ced64 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in writeback_single_inode
2022/09/03 17:25 upstream d895ec7938c4 28811d0a .config console log report info ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in writeback_single_inode
2022/08/18 18:42 upstream 3b06a2755758 d58e263f .config console log report info ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in writeback_single_inode
* Struck through repros no longer work on HEAD.