kernel BUG in ext4_write_inline_data_end

19 views
Skip to first unread message

syzbot

unread,
Apr 29, 2021, 10:18:18 PM4/29/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=134af3f5d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=efcdc581d0554c0d73fd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e9ab5dd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=136470c3d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+efcdc5...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:757!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 9410 Comm: syz-executor282 Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809c7e0500 task.stack: ffff888091790000
RIP: 0010:ext4_write_inline_data_end+0x360/0x490 fs/ext4/inline.c:757
RSP: 0018:ffff8880917974a8 EFLAGS: 00010297
RAX: ffff88809c7e0500 RBX: 1ffff110122f2e99 RCX: 00000000000006be
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88808b516250
RBP: ffff88808b5163f0 R08: ffffffff8b9930b0 R09: 000000000004040f
R10: ffff88809c7e0dd8 R11: ffff88809c7e0500 R12: ffffea00022cc000
R13: 0000000000000001 R14: ffff8880917974e8 R15: ffff88808b516258
FS: 00007f3730c71700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004d36c0 CR3: 000000009a801000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_write_end+0x18d/0xca0 fs/ext4/inode.c:1422
ext4_da_write_end+0x6da/0x8e0 fs/ext4/inode.c:3177
generic_perform_write+0x268/0x420 mm/filemap.c:3066
__generic_file_write_iter+0x42b/0x590 mm/filemap.c:3148
ext4_file_write_iter+0x276/0xd20 fs/ext4/file.c:270
call_write_iter include/linux/fs.h:1778 [inline]
do_iter_readv_writev+0x4cf/0x5f0 fs/read_write.c:675
do_iter_write+0x152/0x550 fs/read_write.c:954
vfs_iter_write+0x70/0xa0 fs/read_write.c:967
iter_file_splice_write+0x52b/0xa90 fs/splice.c:749
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x115/0x160 fs/splice.c:1018
splice_direct_to_actor+0x27c/0x730 fs/splice.c:973
do_splice_direct+0x164/0x210 fs/splice.c:1061
do_sendfile+0x47f/0xb30 fs/read_write.c:1441
SYSC_sendfile64 fs/read_write.c:1502 [inline]
SyS_sendfile64+0xff/0x110 fs/read_write.c:1488
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x44acd9
RSP: 002b:00007f3730c712f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00000000004cd4e0 RCX: 000000000044acd9
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 000000000049d0b4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0030656c69662f2e
R13: 000000000049c0b0 R14: 0000000300000002 R15: 00000000004cd4e8
Code: 3c 02 00 0f 85 29 01 00 00 48 8b 7d 28 44 89 f9 ba ef 02 00 00 45 31 e4 48 c7 c6 a0 13 98 87 e8 b7 99 0c 00 eb 8d e8 00 07 9c ff <0f> 0b e8 f9 06 9c ff 49 8d 7c 24 20 48 89 f8 48 c1 e8 03 42 80
RIP: ext4_write_inline_data_end+0x360/0x490 fs/ext4/inline.c:757 RSP: ffff8880917974a8
---[ end trace 471dc57d81c657fc ]---


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages