syzbot


kernel BUG in ext4_write_inline_data_end (2)

Status: upstream: reported syz repro on 2023/01/25 15:39
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+ba461b83903ea68a8198@syzkaller.appspotmail.com
First crash: 251d, last: 3d23h
Similar bugs (11)
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 261d 1084d 24/25 fixed on 2023/02/24 13:50
android-54 kernel BUG in ext4_write_inline_data_end C 4 445d 579d 2/2 fixed on 2022/09/27 22:24
android-5-10 kernel BUG in ext4_write_inline_data_end C error 3 512d 579d 0/2 closed as dup on 2022/03/04 15:25
android-5-15 kernel BUG in ext4_write_inline_data_end (2) origin:lts C 4 9d20h 9d23h 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 11 7d11h 463d 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 31 15d 205d 0/3 upstream: reported C repro on 2023/03/12 18:03
android-5-15 kernel BUG in ext4_write_inline_data_end C error 11 303d 364d 2/2 fixed on 2023/02/02 00:40
linux-4.19 kernel BUG in ext4_write_inline_data_end ext4 C error 12 215d 961d 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 2 55d 127d 0/3 upstream: reported C repro on 2023/05/30 10:48
upstream kernel BUG in ext4_write_inline_data_end ext4 C error 28 21d 215d 0/25 upstream: reported C repro on 2023/03/02 15:48
linux-4.14 kernel BUG in ext4_write_inline_data_end C error 4 301d 887d 0/1 upstream: reported C repro on 2021/04/30 02:18
Last patch testing requests (3)
Created Duration User Patch Repo Result
2023/09/30 12:24 11m retest repro android12-5.4 report log
2023/07/22 11:20 36m retest repro android12-5.4 report log
2023/05/13 11:00 17m retest repro android12-5.4 report log

Sample crash report:
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:763!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 641 Comm: syz-executor.2 Not tainted 5.4.225-syzkaller-00025-g95647568244a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:ext4_write_inline_data_end+0x4ce/0x4e0 fs/ext4/ext4.h:3237
Code: ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c d4 fd ff ff 4c 89 e7 e8 01 d4 d1 ff e9 c7 fd ff ff e8 a7 37 7a ff e8 42 62 a3 ff <0f> 0b e8 3b 62 a3 ff 0f 0b 66 0f 1f 84 00 00 00 00 00 55 41 57 41
RSP: 0018:ffff8881e5d17760 EFLAGS: 00010293
RAX: ffffffff81c21cce RBX: 0000000000000000 RCX: ffff8881e6112f40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8881e5d17870 R08: ffffffff81c219c4 R09: ffffed103b2d7151
R10: ffffed103b2d7151 R11: 1ffff1103b2d7150 R12: 0000008c00080000
R13: ffff8881d96b8a30 R14: ffffea000760d680 R15: ffff8881d96b8b30
FS:  00007efecabf7700(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001e89e1000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 ext4_write_end+0x1cd/0xe40 fs/ext4/inode.c:1453
 generic_perform_write+0x400/0x5a0 mm/filemap.c:3322
 __generic_file_write_iter+0x239/0x490 mm/filemap.c:3440
 ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270
 call_write_iter include/linux/fs.h:1981 [inline]
 new_sync_write fs/read_write.c:483 [inline]
 __vfs_write+0x5e3/0x780 fs/read_write.c:496
 vfs_write+0x210/0x4f0 fs/read_write.c:558
 ksys_write+0x198/0x2c0 fs/read_write.c:611
 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace e4ebf3e9c5f3d09c ]---
RIP: 0010:ext4_write_inline_data_end+0x4ce/0x4e0 fs/ext4/ext4.h:3237
Code: ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c d4 fd ff ff 4c 89 e7 e8 01 d4 d1 ff e9 c7 fd ff ff e8 a7 37 7a ff e8 42 62 a3 ff <0f> 0b e8 3b 62 a3 ff 0f 0b 66 0f 1f 84 00 00 00 00 00 55 41 57 41
RSP: 0018:ffff8881e5d17760 EFLAGS: 00010293
RAX: ffffffff81c21cce RBX: 0000000000000000 RCX: ffff8881e6112f40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8881e5d17870 R08: ffffffff81c219c4 R09: ffffed103b2d7151
R10: ffffed103b2d7151 R11: 1ffff1103b2d7150 R12: 0000008c00080000
R13: ffff8881d96b8a30 R14: ffffea000760d680 R15: ffff8881d96b8b30
FS:  00007efecabf7700(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff155f7f48 CR3: 00000001e89e1000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/25 16:20 android12-5.4 95647568244a 9dfcf09c .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-4-kasan kernel BUG in ext4_write_inline_data_end
2023/08/03 06:01 android12-5.4 d8e4fb522fec 39a91c18 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-4-kasan kernel BUG in ext4_write_inline_data_end
2023/02/10 11:10 android12-5.4 6a5ec6cea0cd 07980f9d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-4-kasan kernel BUG in ext4_write_inline_data_end
2023/01/25 15:39 android12-5.4 95647568244a 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-4-kasan kernel BUG in ext4_write_inline_data_end
* Struck through repros no longer work on HEAD.