From: syzbot <syzbot+198e7455f3a4f38b838a@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end
Date: Thu, 02 Mar 2023 07:48:58 -0800 [thread overview]
Message-ID: <000000000000562d8105f5ecc4ca@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 2ebd1fbb946d Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13de1350c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3519974f3f27816d
dashboard link: https://syzkaller.appspot.com/bug?extid=198e7455f3a4f38b838a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160fccacc80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e5963cc80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16985cc7a274/disk-2ebd1fbb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fd3452567115/vmlinux-2ebd1fbb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c75510922212/Image-2ebd1fbb.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0427397bf5ad/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+198e7455f3a4f38b838a@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:226!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6191 Comm: syz-executor142 Not tainted 6.2.0-syzkaller-18300-g2ebd1fbb946d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ext4_write_inline_data fs/ext4/inline.c:226 [inline]
pc : ext4_write_inline_data_end+0xe28/0xf84 fs/ext4/inline.c:767
lr : ext4_write_inline_data fs/ext4/inline.c:226 [inline]
lr : ext4_write_inline_data_end+0xe28/0xf84 fs/ext4/inline.c:767
sp : ffff80001eac7520
x29: ffff80001eac7630 x28: ffff0000d7a63680 x27: dfff800000000000
x26: 0000000000000060 x25: ffff80001eac75c0 x24: 0000000040000000
x23: 000000000000006c x22: 0000000000000060 x21: 000000000000000c
x20: ffff0000de2e48e8 x19: 0000000000000000 x18: ffff80001eac70d8
x17: ffff800015b8d000 x16: ffff80001231393c x15: 00000000200002c0
x14: 1ffff00002b720af x13: 0000000000000007 x12: 0000000000000001
x11: ff80800008e4087c x10: 0000000000000000 x9 : ffff800008e4087c
x8 : ffff0000d7a63680 x7 : ffff800008de16f0 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 00000000000008a5 x3 : ffff800008b36a88
x2 : 0000000000000001 x1 : 0000000000000060 x0 : 000000000000006c
Call trace:
ext4_write_inline_data fs/ext4/inline.c:226 [inline]
ext4_write_inline_data_end+0xe28/0xf84 fs/ext4/inline.c:767
ext4_da_write_end+0x330/0x9fc fs/ext4/inode.c:3150
generic_perform_write+0x384/0x55c mm/filemap.c:3784
ext4_buffered_write_iter+0x2e0/0x538 fs/ext4/file.c:285
ext4_file_write_iter+0x188/0x16c0
call_write_iter include/linux/fs.h:2189 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x914 fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591
Code: 14000043 97db2731 d4210000 97db272f (d4210000)
---[ end trace 0000000000000000 ]---
---
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 syzkaller@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
next reply other threads:[~2023-03-02 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:48 syzbot [this message]
2024-01-25 3:17 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end syzbot
2024-01-26 11:05 ` Jan Kara
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=000000000000562d8105f5ecc4ca@google.com \
--to=syzbot+198e7455f3a4f38b838a@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.