From: Dan Carpenter <dan.carpenter@linaro.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
qemu-devel@nongnu.org, "open list" <linux-kernel@vger.kernel.org>,
"Linux Regressions" <regressions@lists.linux.dev>,
linux-ext4 <linux-ext4@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-mm <linux-mm@kvack.org>,
"Linux btrfs" <linux-btrfs@vger.kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>, "Qu Wenruo" <wqu@suse.com>,
"David Sterba" <dsterba@suse.com>
Subject: Re: qemu-arm64: CONFIG_ARM64_64K_PAGES=y kernel crash on qemu-arm64 with Linux next-20241210 and above
Date: Thu, 19 Dec 2024 18:37:30 +0300 [thread overview]
Message-ID: <0c46224b-ed2b-4c8e-aa96-d8f657f59b9f@stanley.mountain> (raw)
In-Reply-To: <a3406049-7ab5-45b9-80bf-46f73ef73a4f@stanley.mountain>
On Thu, Dec 19, 2024 at 06:10:56PM +0300, Dan Carpenter wrote:
> > > Mind to test it with KASAN enabled?
> >
>
> Anders is going to try that later and report back.
>
Anders ran it and emailed me. I was going to tell him to respond to
the thread but I decided to steal the credit. #GreatArtists
BTRFS info (device loop0): using crc32c (crc32c-arm64) checksum algorithm
==================================================================
BUG: KASAN: slab-out-of-bounds in __bitmap_set+0xf8/0x100
Read of size 8 at addr fff0000020e4a3c8 by task chdir01/479
CPU: 1 UID: 0 PID: 479 Comm: chdir01 Not tainted 6.13.0-rc3-next-20241218 #1
Hardware name: linux,dummy-virt (DT)
Call trace:
show_stack+0x20/0x38 (C)
dump_stack_lvl+0x8c/0xd0
print_report+0x118/0x5e0
kasan_report+0xb4/0x100
__asan_report_load8_noabort+0x20/0x30
__bitmap_set+0xf8/0x100
btrfs_subpage_set_uptodate+0xd8/0x1d0 [btrfs]
set_extent_buffer_uptodate+0x1ac/0x288 [btrfs]
__alloc_dummy_extent_buffer+0x2cc/0x488 [btrfs]
alloc_dummy_extent_buffer+0x4c/0x78 [btrfs]
btrfs_check_system_chunk_array+0x30/0x308 [btrfs]
btrfs_validate_super+0x7e8/0xd40 [btrfs]
open_ctree+0x958/0x3c98 [btrfs]
btrfs_get_tree+0xce4/0x13d8 [btrfs]
vfs_get_tree+0x7c/0x290
fc_mount+0x20/0xa8
btrfs_get_tree+0x72c/0x13d8 [btrfs]
vfs_get_tree+0x7c/0x290
path_mount+0x748/0x1518
__arm64_sys_mount+0x234/0x4f8
invoke_syscall.constprop.0+0x78/0x1f0
do_el0_svc+0xcc/0x1d8
el0_svc+0x38/0xa8
el0t_64_sync_handler+0x10c/0x138
el0t_64_sync+0x198/0x1a0
Here are the full logs.
https://people.linaro.org/~anders.roxell/next-20241218-issue-arm64-64k+kasan/
regards,
dan carpenter
next prev parent reply other threads:[~2024-12-19 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 12:03 Naresh Kamboju
2024-12-18 15:52 ` Naresh Kamboju
2024-12-18 17:57 ` David Sterba
2024-12-18 20:07 ` Qu Wenruo
2024-12-19 0:14 ` Qu Wenruo
2024-12-19 15:10 ` Dan Carpenter
2024-12-19 15:37 ` Dan Carpenter [this message]
2024-12-19 23:33 ` Qu Wenruo
2024-12-19 23:20 ` Qu Wenruo
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=0c46224b-ed2b-4c8e-aa96-d8f657f59b9f@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=regressions@lists.linux.dev \
--cc=wqu@suse.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