From: syzbot <syzbot+f3185be57d7e8dda32b8@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (3)
Date: Sat, 18 Oct 2025 08:35:03 -0700 [thread overview]
Message-ID: <68f3b3a7.050a0220.1186a4.0520.GAE@google.com> (raw)
In-Reply-To: <20251018151148.411120-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in __ext4_journal_stop
------------[ cut here ]------------
kernel BUG at fs/ext4/ext4_jbd2.c:54!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 7268 Comm: syz.3.141 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:54 [inline]
RIP: 0010:__ext4_journal_stop+0x191/0x1a0 fs/ext4/ext4_jbd2.c:126
Code: e8 e4 3e 50 ff e9 f8 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 10 ff ff ff e8 ba ee b5 ff e9 06 ff ff ff e8 c0 3e 50 ff 90 <0f> 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90
RSP: 0018:ffffc9000b107840 EFLAGS: 00010293
RAX: ffffffff826f6420 RBX: 0000000000000000 RCX: ffff88802e085ac0
RDX: 0000000000000000 RSI: 0000000000000361 RDI: ffffffff8d5e2286
RBP: ffffc9000b107968 R08: ffffea000175b077 R09: 1ffffd40002eb60e
R10: dffffc0000000000 R11: fffff940002eb60f R12: 0000000000000078
R13: 0000000000000361 R14: ffffffff8d5e2286 R15: ffff888074bb6bc8
FS: 00007ff117be16c0(0000) GS:ffff88812646b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555564fe588 CR3: 00000000546e9000 CR4: 0000000000350ef0
Call Trace:
<TASK>
ext4_write_inline_data_end+0x7a9/0xab0 fs/ext4/inline.c:865
generic_perform_write+0x62a/0x900 mm/filemap.c:4263
ext4_buffered_write_iter+0xce/0x3a0 fs/ext4/file.c:299
ext4_file_write_iter+0x298/0x1bc0 fs/ext4/file.c:-1
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x5c9/0xb30 fs/read_write.c:686
ksys_write+0x145/0x250 fs/read_write.c:738
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff116d8eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff117be1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff116fe5fa0 RCX: 00007ff116d8eec9
RDX: 0000000000000078 RSI: 0000200000000600 RDI: 0000000000000005
RBP: 00007ff116e11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff116fe6038 R14: 00007ff116fe5fa0 R15: 00007ffd5125ed68
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:54 [inline]
RIP: 0010:__ext4_journal_stop+0x191/0x1a0 fs/ext4/ext4_jbd2.c:126
Code: e8 e4 3e 50 ff e9 f8 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 10 ff ff ff e8 ba ee b5 ff e9 06 ff ff ff e8 c0 3e 50 ff 90 <0f> 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90
RSP: 0018:ffffc9000b107840 EFLAGS: 00010293
RAX: ffffffff826f6420 RBX: 0000000000000000 RCX: ffff88802e085ac0
RDX: 0000000000000000 RSI: 0000000000000361 RDI: ffffffff8d5e2286
RBP: ffffc9000b107968 R08: ffffea000175b077 R09: 1ffffd40002eb60e
R10: dffffc0000000000 R11: fffff940002eb60f R12: 0000000000000078
R13: 0000000000000361 R14: ffffffff8d5e2286 R15: ffff888074bb6bc8
FS: 00007ff117be16c0(0000) GS:ffff88812636b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555593914808 CR3: 00000000546e9000 CR4: 0000000000350ef0
Tested on:
commit: f406055c Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=173b2b04580000
kernel config: https://syzkaller.appspot.com/x/.config?x=308983f9c02338e8
dashboard link: https://syzkaller.appspot.com/bug?extid=f3185be57d7e8dda32b8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=17b5767c580000
next parent reply other threads:[~2025-10-18 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251018151148.411120-1-kartikey406@gmail.com>
2025-10-18 15:35 ` syzbot [this message]
[not found] <CADfthj2kwRdbSo1PJPFnztaSv2hXC+Oo9q2PCTNDEwSKknoLkg@mail.gmail.com>
2025-11-11 6:38 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data (3) syzbot
[not found] <CADfthj3aOC17CsRgB13PKvD6s4VFKNC1yUMVfkmdj2AZE+rTDw@mail.gmail.com>
2025-11-11 2:52 ` syzbot
[not found] <CADfthj1wOFy2SijFsSHPSCLBe7EQ7-b_AYkD39=83zUfYbQiow@mail.gmail.com>
2025-11-10 22:20 ` syzbot
[not found] <20251020050706.473196-1-kartikey406@gmail.com>
2025-10-20 5:32 ` syzbot
[not found] <CADfthj2CUn1dQPVaoxHZ2x-6Jppnyf5gbETxOun+-05_OmXLGA@mail.gmail.com>
2025-10-09 3:09 ` syzbot
[not found] <CAHxJ8O-VdrVEyCpktyUnEE-xwsN8poMvYsXsmQFfwvxi8f-E0g@mail.gmail.com>
2025-10-07 23:25 ` syzbot
2025-09-13 15:21 syzbot
2025-10-03 1:55 ` syzbot
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=68f3b3a7.050a0220.1186a4.0520.GAE@google.com \
--to=syzbot+f3185be57d7e8dda32b8@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.