From: David Sterba <dsterba@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: 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>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"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: Wed, 18 Dec 2024 18:57:16 +0100 [thread overview]
Message-ID: <20241218175716.GD31418@twin.jikos.cz> (raw)
In-Reply-To: <CA+G9fYv7_fMKOxA8DB8aUnsDjQ9TX8OQtHVRcRQkFGqdD0vjNQ@mail.gmail.com>
On Wed, Dec 18, 2024 at 09:22:26PM +0530, Naresh Kamboju wrote:
> On Wed, 18 Dec 2024 at 17:33, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > The following kernel crash noticed on qemu-arm64 while running the
> > Linux next-20241210 tag (to next-20241218) kernel built with
> > - CONFIG_ARM64_64K_PAGES=y
> > - CONFIG_ARM64_16K_PAGES=y
> > and running LTP smoke tests.
> >
> > First seen on Linux next-20241210.
> > Good: next-20241209
> > Bad: next-20241210 and next-20241218
> >
> > qemu-arm64: 9.1.2
> >
> > Anyone noticed this ?
> >
>
> Anders bisected this reported regression and found,
> # first bad commit:
> [9c1d66793b6faa00106ae4c866359578bfc012d2]
> btrfs: validate system chunk array at btrfs_validate_super()
Thanks, I'll drop the patch from linux-next for now.
next prev parent reply other threads:[~2024-12-18 17:57 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 [this message]
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
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=20241218175716.GD31418@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--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=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