All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+53c8bd6136cfbe85197e@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, jack@suse.cz,
	libaokun@linux.alibaba.com,  linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org,  ojaswin@linux.ibm.com,
	ritesh.list@gmail.com, syzkaller-bugs@googlegroups.com,
	 tytso@mit.edu, yi.zhang@huawei.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (5)
Date: Fri, 10 Jul 2026 18:29:35 -0700	[thread overview]
Message-ID: <6a519c7f.278cdcd2.e885.000c.GAE@google.com> (raw)
In-Reply-To: <6a27cb2a.39669fcc.33b062.008b.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    a635d6748234 Merge tag 'v7.2-rc2-smb3-server-fixes' of git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10c8b0b9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8578cb30af0c1c29
dashboard link: https://syzkaller.appspot.com/bug?extid=53c8bd6136cfbe85197e
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12d41346580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5cfb3b35578d/disk-a635d674.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f49a13f1718/vmlinux-a635d674.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1c79dac0ba82/bzImage-a635d674.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e19a0b652c4c/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=125ac0b9580000)

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

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:240!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 6277 Comm: syz.5.64 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:ext4_write_inline_data+0x40b/0x4f0 fs/ext4/inline.c:240
Code: fe e8 e9 e7 36 ff 42 8d 44 23 c4 bb 3c 00 00 00 89 44 24 08 44 29 e3 e9 aa fe ff ff e8 ce e7 36 ff 90 0f 0b e8 c6 e7 36 ff 90 <0f> 0b e8 be e7 36 ff 48 8d 3d f7 52 56 0e 48 c7 c2 e0 95 ed 8b 4c
RSP: 0018:ffffc90003d7f8e0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000078 RCX: ffffffff82d2c53b
RDX: ffff8880280cdd00 RSI: ffffffff82d2c75a RDI: ffff8880280cdd00
RBP: ffff88807127e000 R08: 0000000000000006 R09: 0000000000000080
R10: 000000000000003c R11: 0000000000000000 R12: 0000000000000008
R13: 0000000000000080 R14: ffffc90003d7f980 R15: ffff88807127e58a
FS:  00007f45fb4396c0(0000) GS:ffff888123eed000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff59e5b7000 CR3: 000000007855a000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 ext4_write_inline_data_end+0x2a8/0xdb0 fs/ext4/inline.c:825
 ext4_da_write_end+0x51e/0xe70 fs/ext4/inode.c:3305
 generic_perform_write+0x513/0xa40 mm/filemap.c:4379
 ext4_buffered_write_iter+0xdc/0x3b0 fs/ext4/file.c:316
 ext4_file_write_iter+0xa2f/0x1cb0 fs/ext4/file.c:735
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6ac/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f45fa59de59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f45fb439028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f45fa825fa0 RCX: 00007f45fa59de59
RDX: 0000000000000078 RSI: 00002000000000c0 RDI: 0000000000000004
RBP: 00007f45fa633e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f45fa826038 R14: 00007f45fa825fa0 R15: 00007fff8e2c70e8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_write_inline_data+0x40b/0x4f0 fs/ext4/inline.c:240
Code: fe e8 e9 e7 36 ff 42 8d 44 23 c4 bb 3c 00 00 00 89 44 24 08 44 29 e3 e9 aa fe ff ff e8 ce e7 36 ff 90 0f 0b e8 c6 e7 36 ff 90 <0f> 0b e8 be e7 36 ff 48 8d 3d f7 52 56 0e 48 c7 c2 e0 95 ed 8b 4c
RSP: 0018:ffffc90003d7f8e0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000078 RCX: ffffffff82d2c53b
RDX: ffff8880280cdd00 RSI: ffffffff82d2c75a RDI: ffff8880280cdd00
RBP: ffff88807127e000 R08: 0000000000000006 R09: 0000000000000080
R10: 000000000000003c R11: 0000000000000000 R12: 0000000000000008
R13: 0000000000000080 R14: ffffc90003d7f980 R15: ffff88807127e58a
FS:  00007f45fb4396c0(0000) GS:ffff888123ded000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff59e5b6000 CR3: 000000007855a000 CR4: 0000000000350ef0


---
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.

      reply	other threads:[~2026-07-11  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  8:13 [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (5) syzbot
2026-07-11  1:29 ` syzbot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a519c7f.278cdcd2.e885.000c.GAE@google.com \
    --to=syzbot+53c8bd6136cfbe85197e@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.