syzbot

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

invalid opcode in writeback_single_inode

Status: auto-obsoleted due to no activity on 2023/12/23 05:18
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+15cb24a539075fc4c472@syzkaller.appspotmail.com
First crash: 906d, last: 658d
Cause bisection: introduced by (bisect log) :
commit 6e5be40d32fb1907285277c02e74493ed43d77fe
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Aug 13 14:21:30 2021 +0000

  fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile

Crash: KASAN: out-of-bounds Write in end_buffer_read_sync (log)
Repro: C syz .config
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] invalid opcode in writeback_single_inode 0 (2) 2022/10/02 18:22
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2023/12/23 04:44 26m retest repro upstream OK log
2023/12/23 04:44 22m retest repro upstream OK log
2023/10/14 03:53 21m retest repro upstream report log
2023/10/14 03:53 23m retest repro upstream report log
2023/09/08 18:35 25m retest repro upstream OK log
2023/08/05 00:10 43m retest repro upstream report log
2023/08/05 00:10 34m retest repro upstream report log
▶ ▼ Fix bisection attempts (7)
Created Duration User Patch Repo Result
2023/06/28 12:28 28m bisect fix upstream OK (0) job log
2023/05/26 18:25 31m bisect fix upstream OK (0) job log log
2023/04/26 16:09 29m bisect fix upstream OK (0) job log log
2023/03/27 11:20 33m bisect fix upstream OK (0) job log log
2023/02/25 00:05 27m bisect fix upstream OK (0) job log log
2023/01/25 23:29 32m bisect fix upstream OK (0) job log log
2022/11/07 23:26 31m bisect fix upstream OK (0) job log log

Sample crash report:
loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3778 Comm: syz-executor421 Not tainted 6.0.0-syzkaller-00372-ga5088ee7251e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 69 4d 98 ff 4c 89 f7 e8 41 a8 9f <07> be 04 00 00 00 4c 89 ef e8 54 b7 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90003bdfa10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff9200077bf4b RCX: ffffffff815ff450
RDX: 1ffff1100ca236d1 RSI: 0000000000000004 RDI: ffffc90003bdf9a0
RBP: ffff88806511b5f0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff5200077bf34 R11: 0000000000000000 R12: ffffc90003bdfa88
R13: ffff88806511b7f8 R14: ffff88806511b678 R15: ffff88806511b6c8
FS:  0000555557259300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4c585e6c10 CR3: 0000000075602000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
 iput_final fs/inode.c:1735 [inline]
 iput.part.0+0x45b/0x810 fs/inode.c:1774
 iput+0x58/0x70 fs/inode.c:1764
 ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x440/0x760 fs/super.c:1323
 vfs_get_tree+0x89/0x2f0 fs/super.c:1530
 do_new_mount fs/namespace.c:3040 [inline]
 path_mount+0x1326/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4c5861343a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 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:00007ffe4de07d58 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f4c5861343a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffe4de07d70
RBP: 00007ffe4de07d70 R08: 00007ffe4de07db0 R09: 00005555572592c0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffe4de07db0 R14: 0000000000000219 R15: 0000000020003458
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 69 4d 98 ff 4c 89 f7 e8 41 a8 9f <07> be 04 00 00 00 4c 89 ef e8 54 b7 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90003bdfa10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff9200077bf4b RCX: ffffffff815ff450
RDX: 1ffff1100ca236d1 RSI: 0000000000000004 RDI: ffffc90003bdf9a0
RBP: ffff88806511b5f0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff5200077bf34 R11: 0000000000000000 R12: ffffc90003bdfa88
R13: ffff88806511b7f8 R14: ffff88806511b678 R15: ffff88806511b6c8
FS:  0000555557259300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4c585e6c10 CR3: 0000000075602000 CR4: 0000000000350ef0

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/05 05:43 upstream a5088ee7251e eab8f949 .config console log report syz C [disk image] [vmlinux] [mounted in repro] ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/10/03 04:41 upstream a962b54e162c feb56351 .config strace log report syz C [disk image] [vmlinux] ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/10/02 18:22 upstream b357fd1c2afc feb56351 .config console log report syz C [disk image] [vmlinux] ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/10/05 09:31 upstream 2bca25eaeba6 eab8f949 .config console log report info ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/10/03 14:38 upstream 4fe89d07dcc2 feb56351 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/09/29 14:00 upstream c3e0e1e23c70 1d385642 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/09/28 06:37 upstream 46452d3786a8 75c78242 .config console log report info ci-upstream-kasan-gce-selinux-root invalid opcode in writeback_single_inode
2022/09/28 05:49 upstream 46452d3786a8 75c78242 .config console log report info ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/09/28 03:00 upstream 46452d3786a8 75c78242 .config console log report info ci-qemu-upstream invalid opcode in writeback_single_inode
2022/09/26 17:44 upstream f76349cf4145 d59ba983 .config console log report info ci-upstream-kasan-gce-root invalid opcode in writeback_single_inode
2022/09/22 18:01 upstream dc164f4fb00a 0042f2b4 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-selinux-root invalid opcode in writeback_single_inode
2022/09/20 01:51 upstream 521a547ced64 dd9a85ff .config console log report info ci-upstream-kasan-gce-selinux-root invalid opcode in writeback_single_inode
* Struck through repros no longer work on HEAD.