syzbot


kernel BUG in ext4_write_inline_data_end

Status: upstream: reported C repro on 2021/04/30 02:18
Reported-by: syzbot+efcdc581d0554c0d73fd@syzkaller.appspotmail.com
First crash: 1321d, last: 735d
Fix bisection: failed (error log, bisect log)
  
Similar bugs (13)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG at fs/ext4/inline.c:LINE! ext4 C done done 76 695d 1518d 22/28 fixed on 2023/02/24 13:50
android-54 kernel BUG in ext4_write_inline_data_end C 4 879d 1013d 2/2 fixed on 2022/09/27 22:24
android-5-10 kernel BUG in ext4_write_inline_data_end C error 3 946d 1013d 0/2 closed as dup on 2022/03/04 15:25
android-5-15 kernel BUG in ext4_write_inline_data_end (2) origin:upstream C 9 27d 443d 0/2 upstream: reported C repro on 2023/09/24 12:05
android-5-10 kernel BUG in ext4_write_inline_data_end (2) C error 13 230d 897d 2/2 upstream: reported C repro on 2022/06/27 15:18
linux-6.1 kernel BUG in ext4_write_inline_data_end origin:upstream C error 43 23d 639d 0/3 upstream: reported C repro on 2023/03/12 18:03
android-6-1 kernel BUG in ext4_write_inline_data_end origin:lts C error done 1 60d 392d 0/2 upstream: reported C repro on 2023/11/14 10:56
android-5-15 kernel BUG in ext4_write_inline_data_end C error 11 737d 797d 2/2 fixed on 2023/02/02 00:40
linux-4.19 kernel BUG in ext4_write_inline_data_end ext4 C error 12 648d 1395d 0/1 upstream: reported C repro on 2021/02/14 13:39
linux-5.15 kernel BUG in ext4_write_inline_data_end origin:upstream C error 4 65d 560d 0/3 upstream: reported C repro on 2023/05/30 10:48
upstream kernel BUG in ext4_write_inline_data_end ext4 C error done 32 351d 649d 25/28 fixed on 2024/01/30 23:26
android-54 kernel BUG in ext4_write_inline_data_end (2) ext4 syz 9 63d 685d 0/2 upstream: reported syz repro on 2023/01/25 15:39
upstream kernel BUG in ext4_write_inline_data_end (2) ext4 C inconclusive 121 1d13h 312d 0/28 upstream: reported C repro on 2024/02/02 09:24
Last patch testing requests (3)
Created Duration User Patch Repo Result
2022/12/02 16:30 12m retest repro linux-4.14.y report log
2022/12/02 05:30 10m retest repro linux-4.14.y report log
2022/12/02 03:30 11m retest repro linux-4.14.y report log
Fix bisection attempts (12)
Created Duration User Patch Repo Result
2022/05/03 19:03 14m bisect fix linux-4.14.y error job log
2022/04/03 18:33 29m bisect fix linux-4.14.y OK (0) job log log
2022/02/26 15:23 23m bisect fix linux-4.14.y OK (0) job log log
2022/01/27 14:52 30m bisect fix linux-4.14.y OK (0) job log log
2021/12/28 14:20 25m bisect fix linux-4.14.y OK (0) job log log
2021/11/28 13:49 22m bisect fix linux-4.14.y OK (0) job log log
2021/10/29 13:09 22m bisect fix linux-4.14.y OK (0) job log log
2021/09/27 03:55 26m bisect fix linux-4.14.y OK (0) job log log
2021/08/28 03:29 25m bisect fix linux-4.14.y OK (0) job log log
2021/07/29 03:02 26m bisect fix linux-4.14.y OK (0) job log log
2021/06/29 02:40 22m bisect fix linux-4.14.y OK (0) job log log
2021/05/30 02:17 22m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:760!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 17898 Comm: syz-executor261 Not tainted 4.14.300-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff88808f5ca400 task.stack: ffff8880a63e0000
RIP: 0010:ext4_write_inline_data_end+0x368/0x490 fs/ext4/inline.c:760
RSP: 0018:ffff8880a63e7930 EFLAGS: 00010297
RAX: ffff88808f5ca400 RBX: 1ffff11014c7cf2a RCX: 000000000000254f
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88808a41c610
RBP: ffff88808a41c7b0 R08: ffffffff8b9b2578 R09: 0000000000040408
R10: ffff88808f5cad00 R11: ffff88808f5ca400 R12: ffffea00022a2ac0
R13: 0000000000000020 R14: ffff8880a63e7970 R15: ffff88808a41c618
FS:  00007fea8fa6a700(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564e0e9dc160 CR3: 00000000af999000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 ext4_write_end+0x18d/0xca0 fs/ext4/inode.c:1429
 ext4_da_write_end+0x6da/0x8e0 fs/ext4/inode.c:3216
 generic_perform_write+0x274/0x430 mm/filemap.c:3066
 __generic_file_write_iter+0x227/0x590 mm/filemap.c:3180
 ext4_file_write_iter+0x276/0xd20 fs/ext4/file.c:270
 call_write_iter include/linux/fs.h:1780 [inline]
 new_sync_write fs/read_write.c:469 [inline]
 __vfs_write+0x44c/0x630 fs/read_write.c:482
 vfs_write+0x17f/0x4d0 fs/read_write.c:544
 SYSC_write fs/read_write.c:590 [inline]
 SyS_write+0xf2/0x210 fs/read_write.c:582
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
Code: 3c 02 00 0f 85 29 01 00 00 48 8b 7d 28 44 89 f9 ba f2 02 00 00 45 31 e4 48 c7 c6 20 33 98 87 e8 6f ad 0c 00 eb 8d e8 e8 cc 9b ff <0f> 0b e8 e1 cc 9b ff 49 8d 7c 24 20 48 89 f8 48 c1 e8 03 42 80 
RIP: ext4_write_inline_data_end+0x368/0x490 fs/ext4/inline.c:760 RSP: ffff8880a63e7930
---[ end trace 5104a7425bba67c3 ]---

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/12/06 15:40 linux-4.14.y 179ef7fe8677 045cbb84 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 kernel BUG in ext4_write_inline_data_end
2022/08/24 03:18 linux-4.14.y b641242202ed cea8b0f7 .config console log report syz C ci2-linux-4-14 kernel BUG in ext4_write_inline_data_end
2022/03/04 09:54 linux-4.14.y e853993d29aa 45a13a73 .config console log report syz C ci2-linux-4-14 kernel BUG in ext4_write_inline_data_end
2021/04/30 02:17 linux-4.14.y 7d7d1c0ab3eb 77e2b668 .config console log report syz C ci2-linux-4-14 kernel BUG in ext4_write_inline_data_end
* Struck through repros no longer work on HEAD.