From: Jun Nie <jun.nie@linaro.org>
To: harshadshirwadkar@gmail.com, tytso@mit.edu,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Lee Jones <joneslee@google.com>
Subject: [BUG REPORT] kernel BUG in ext4_write_inline_data_end
Date: Thu, 17 Nov 2022 15:55:35 +0800 [thread overview]
Message-ID: <CABymUCOsVcpaS+uXqzB7-hm0FZwm2ZXD8J=6m0NKAh8WyrTiwA@mail.gmail.com> (raw)
Hi,
syzbot find a bug[0] in ext4 on android13-5.15-lts as below and it can
be reproduced on mailine v6.1-rc5(094226ad94f4) too The log from
mainline can be found in URL [1]. The bisect test shows below
commit[2] is the first commit that reproduce the bug. With reverting
the commit, there is no bug reproduced[3].
Is reverting the commit 21175ca434c5 a acceptable solution? Any fix
work is in progress?
[0] https://syzkaller.appspot.com/bug?id=5bafe4554067100b70f58a81268aa06ea3f9c345
[1] https://syzkaller.appspot.com/text?tag=CrashLog&x=118359c1880000
[2] 21175ca434c5 ext4: make prefetch_block_bitmaps default
[3] https://groups.google.com/g/syzkaller-android-bugs/c/HKLNVJQICMM/m/YcHNpH_iBAAJ
kernel BUG at fs/ext4/inline.c:227!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Call Trace:
<TASK>
ext4_write_end+0x1af/0x9d0 fs/ext4/inode.c:1307
ext4_da_write_end+0x92/0xa70 fs/ext4/inode.c:3067
generic_perform_write+0x3c7/0x5d0 mm/filemap.c:3836
ext4_buffered_write_iter+0x49b/0x630 fs/ext4/file.c:271
ext4_file_write_iter+0x456/0x1dc0
do_iter_readv_writev+0x52a/0x720
do_iter_write+0x1f4/0x760 fs/read_write.c:855
vfs_iter_write+0x7c/0xa0 fs/read_write.c:896
iter_file_splice_write+0x810/0xfd0 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0xfe/0x130 fs/splice.c:934
splice_direct_to_actor+0x4d4/0xbd0 fs/splice.c:889
do_splice_direct+0x2a0/0x3f0 fs/splice.c:977
do_sendfile+0x63b/0xfd0 fs/read_write.c:1249
__do_sys_sendfile64 fs/read_write.c:1317 [inline]
__se_sys_sendfile64 fs/read_write.c:1303 [inline]
__x64_sys_sendfile64+0x1ce/0x230 fs/read_write.c:1303
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Regards,
Jun
next reply other threads:[~2022-11-17 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 7:55 Jun Nie [this message]
2022-12-05 8:54 ` [BUG REPORT] kernel BUG in ext4_write_inline_data_end or ext4_writepages Jun Nie
2022-12-07 6:39 ` yebin (H)
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='CABymUCOsVcpaS+uXqzB7-hm0FZwm2ZXD8J=6m0NKAh8WyrTiwA@mail.gmail.com' \
--to=jun.nie@linaro.org \
--cc=adilger.kernel@dilger.ca \
--cc=harshadshirwadkar@gmail.com \
--cc=joneslee@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.