Hello,
syzbot found the following issue on:
HEAD commit: f32b52534f1d Merge android13-5.15 into android13-5.15-lts
git tree: android13-5.15-lts
console+strace:
https://syzkaller.appspot.com/x/log.txt?x=12a8c1f0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=993c2ef7baf0a232
dashboard link:
https://syzkaller.appspot.com/bug?extid=3c7e0a4e0a706e03cb85
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=13647a62580000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=17647a62580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/3fdaf4ddba90/disk-f32b5253.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/0684c5bc4ab1/vmlinux-f32b5253.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/73083400a79f/bzImage-f32b5253.xz
mounted in repro #1:
https://storage.googleapis.com/syzbot-assets/eec0afce6b97/mount_0.gz
fsck result: failed (log:
https://syzkaller.appspot.com/x/fsck.log?x=11647a62580000)
mounted in repro #2:
https://storage.googleapis.com/syzbot-assets/cf9b3155bb5f/mount_5.gz
fsck result: failed (log:
https://syzkaller.appspot.com/x/fsck.log?x=1154ce34580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3c7e0a...@syzkaller.appspotmail.com
kernel BUG at fs/ext4/inline.c:302!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 302 Comm: syz-executor767 Not tainted 5.15.189-syzkaller-android13-5.15.189_r00 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ext4_create_inline_data+0x416/0x420 fs/ext4/inline.c:302
Code: ff ff e8 3d 20 d0 ff e9 0f ff ff ff 89 f9 80 e1 07 fe c1 38 c1 0f 8c 26 ff ff ff e8 24 20 d0 ff e9 1c ff ff ff e8 da a4 91 ff <0f> 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 53 48 89 fb
RSP: 0018:ffffc90000b172c0 EFLAGS: 00010293
RAX: ffffffff81d70af6 RBX: 0000000000000000 RCX: ffff8881049ce2c0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b173f0 R08: 0000000000000000 R09: ffffed1021997528
R10: ffffed1021997528 R11: 1ffff11021997527 R12: ffff88810ccbaa40
R13: 1ffff92000162e5c R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f199e13d6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc18b2fa000 CR3: 000000011ed1b000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_prepare_inline_data+0x16c/0x1f0 fs/ext4/inline.c:413
ext4_try_to_write_inline_data+0x317/0x1110 fs/ext4/inline.c:704
ext4_write_begin+0x221/0x1220 fs/ext4/inode.c:1192
generic_perform_write+0x2ad/0x670 mm/filemap.c:3869
ext4_buffered_write_iter+0x4ed/0x670 fs/ext4/file.c:270
ext4_file_write_iter+0x18c/0x14c0 fs/ext4/file.c:664
call_write_iter include/linux/fs.h:2212 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x802/0xf70 fs/read_write.c:594
ksys_write+0x140/0x240 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
x64_sys_call+0x8ef/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f199e180df9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f199e13d218 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f199e2096c8 RCX: 00007f199e180df9
RDX: 0000000000000012 RSI: 0000200000000100 RDI: 0000000000000004
RBP: 00007f199e2096c0 R08: 00007f199e13cfb7 R09: 0000000000000000
R10: 0000000000000012 R11: 0000000000000246 R12: 00007f199e1d5a10
R13: 0000200000000000 R14: 00007f199e1d5083 R15: 0000200000000100
</TASK>
Modules linked in:
---[ end trace b709cf3a0f716ea9 ]---
RIP: 0010:ext4_create_inline_data+0x416/0x420 fs/ext4/inline.c:302
Code: ff ff e8 3d 20 d0 ff e9 0f ff ff ff 89 f9 80 e1 07 fe c1 38 c1 0f 8c 26 ff ff ff e8 24 20 d0 ff e9 1c ff ff ff e8 da a4 91 ff <0f> 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 53 48 89 fb
RSP: 0018:ffffc90000b172c0 EFLAGS: 00010293
RAX: ffffffff81d70af6 RBX: 0000000000000000 RCX: ffff8881049ce2c0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b173f0 R08: 0000000000000000 R09: ffffed1021997528
R10: ffffed1021997528 R11: 1ffff11021997527 R12: ffff88810ccbaa40
R13: 1ffff92000162e5c R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f199e13d6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc18b2fa000 CR3: 000000011ed1b000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup