From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>, Marc Zyngier <maz@kernel.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Oliver Upton <oupton@kernel.org>,
Aishwarya.TCV@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: -next boot failures during KVM setup
Date: Tue, 9 Jun 2026 09:36:18 +0100 [thread overview]
Message-ID: <aifQgvnDaGiTXN8a@sirena.co.uk> (raw)
In-Reply-To: <20260608232753.GA2993766@ax162>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Mon, Jun 08, 2026 at 04:27:53PM -0700, Nathan Chancellor wrote:
> On Mon, Jun 08, 2026 at 10:56:12PM +0200, Ard Biesheuvel wrote:
> > Given we're at -rc7, I'd lean towards dropping the whole branch for now, or
> > alternatively, only drop/revert "arm64: mm: Unmap kernel data/bss entirely from the
> > linear map" (and its followup fix "arm64: mm: Defer remap of linear alias of
> > data/bss") so that the region always remains readable via the linear map.
> FWIW, I can confirm that "arm64: mm: Unmap kernel data/bss entirely from
> the linear map" is the culprit for this particular issue based on my
> bisect. Reverting those two changes on top of next-20260608 avoids the
> issue.
Yes, same result here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-06-09 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 19:19 -next boot failures during KVM setup Mark Brown
2026-06-08 20:18 ` Marc Zyngier
2026-06-08 20:56 ` Ard Biesheuvel
2026-06-08 23:27 ` Nathan Chancellor
2026-06-09 8:36 ` Mark Brown [this message]
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=aifQgvnDaGiTXN8a@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=nathan@kernel.org \
--cc=oupton@kernel.org \
--cc=will@kernel.org \
/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