public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0c89d865531d053abb2d@syzkaller.appspotmail.com>
To: crashfixer001@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (2)
Date: Fri, 08 Nov 2024 01:38:03 -0800	[thread overview]
Message-ID: <672ddbfb.050a0220.3d9cb.000b.GAE@google.com> (raw)
In-Reply-To: <173105740149.2293654.8622543419878528605@GCRAZCDL0021.westus2.cloudapp.azure.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in ext4_write_inline_data_end

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:235!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 6674 Comm: syz-executor.4 Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:235 [inline]
RIP: 0010:ext4_write_inline_data_end+0xea2/0x1020 fs/ext4/inline.c:774
Code: 31 ff e8 e1 b8 37 ff 48 89 d8 48 25 ff 0f 00 00 74 70 e8 f1 b3 37 ff e9 12 f8 ff ff e8 e7 b3 37 ff 90 0f 0b e8 df b3 37 ff 90 <0f> 0b 48 8b 5c 24 18 48 89 df be 08 00 00 00 e8 ca 81 a1 ff 48 c1
RSP: 0018:ffffc9000a277860 EFLAGS: 00010293
RAX: ffffffff825cffc1 RBX: 000000000000003c RCX: ffff888027cf1e00
RDX: 0000000000000000 RSI: 000000000000003c RDI: 000000000000084c
RBP: ffffc9000a277988 R08: ffffffff825cf51a R09: 1ffff1100fd48070
R10: dffffc0000000000 R11: ffffed100fd48071 R12: ffff888061e6085a
R13: 000000000000000c R14: 000000000000084c R15: 0000000000000ff4
FS:  00007f5978d5b6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1b72ca0000 CR3: 000000007fb3e000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 generic_perform_write+0x4dd/0x6d0 mm/filemap.c:4069
 ext4_buffered_write_iter+0xc5/0x350 fs/ext4/file.c:299
 ext4_file_write_iter+0x1dd/0x1a20
 new_sync_write fs/read_write.c:590 [inline]
 vfs_write+0xaed/0xd30 fs/read_write.c:683
 ksys_write+0x183/0x2b0 fs/read_write.c:736
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f597807dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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:00007f5978d5b0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f59781ac050 RCX: 00007f597807dda9
RDX: 000000000208e24b RSI: 00000000200007c0 RDI: 0000000000000005
RBP: 00007f59780ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f59781ac050 R15: 00007ffe99c38908
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:235 [inline]
RIP: 0010:ext4_write_inline_data_end+0xea2/0x1020 fs/ext4/inline.c:774
Code: 31 ff e8 e1 b8 37 ff 48 89 d8 48 25 ff 0f 00 00 74 70 e8 f1 b3 37 ff e9 12 f8 ff ff e8 e7 b3 37 ff 90 0f 0b e8 df b3 37 ff 90 <0f> 0b 48 8b 5c 24 18 48 89 df be 08 00 00 00 e8 ca 81 a1 ff 48 c1
RSP: 0018:ffffc9000a277860 EFLAGS: 00010293
RAX: ffffffff825cffc1 RBX: 000000000000003c RCX: ffff888027cf1e00
RDX: 0000000000000000 RSI: 000000000000003c RDI: 000000000000084c
RBP: ffffc9000a277988 R08: ffffffff825cf51a R09: 1ffff1100fd48070
R10: dffffc0000000000 R11: ffffed100fd48071 R12: ffff888061e6085a
R13: 000000000000000c R14: 000000000000084c R15: 0000000000000ff4
FS:  00007f5978d5b6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020658000 CR3: 000000007fb3e000 CR4: 0000000000350ef0


Tested on:

commit:         906bd684 Merge tag 'spi-fix-v6.12-rc6' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154ccea7980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ef3e3033284fe956
dashboard link: https://syzkaller.appspot.com/bug?extid=0c89d865531d053abb2d
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.

       reply	other threads:[~2024-11-08  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173105740149.2293654.8622543419878528605@GCRAZCDL0021.westus2.cloudapp.azure.com>
2024-11-08  9:38 ` syzbot [this message]
     [not found] <173106166139.2299330.8314210328501109966@GCRAZCDL0021.westus2.cloudapp.azure.com>
2024-11-08 10:48 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (2) syzbot
2024-02-06 15:44 xingwei lee
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02  9:24 syzbot
2024-02-06 22:48 ` 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=672ddbfb.050a0220.3d9cb.000b.GAE@google.com \
    --to=syzbot+0c89d865531d053abb2d@syzkaller.appspotmail.com \
    --cc=crashfixer001@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox