All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Hsin-Te Yuan <yuanhsinte@chromium.org>
Cc: Brian Norris <briannorris@chromium.org>,
	Julius Werner <jwerner@chromium.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
	Yidi Lin <yidilin@google.com>
Subject: Re: [PATCH v2] firmware: google: coreboot_table: skip no-map CBMEM entries
Date: Mon, 20 Jul 2026 02:56:56 +0000	[thread overview]
Message-ID: <al2OePSmQNG5zkwx@google.com> (raw)
In-Reply-To: <20260717-coreboot-v2-1-8f8b389e3758@chromium.org>

On Fri, Jul 17, 2026 at 08:41:26AM +0000, Hsin-Te Yuan wrote:
> From: Yidi Lin <yidilin@google.com>
> 
> On ARM64 platforms, certain reserved memory regions (like those used
> by pKVM) are marked with the 'no-map' property. This indicates that
> the host kernel is forbidden from creating a structural mapping for
> these regions.
> 
> The coreboot table may describe CBMEM entries that overlap with or are
> entirely contained within these no-map regions. Attempting to populate
> these entries as devices and subsequently remapping them can lead to
> system crashes or security violations.
> 
> [...]

Applied to

    https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-firmware-next

[1/1] firmware: google: coreboot_table: skip no-map CBMEM entries
      commit: e31ecda9e3af675bc05039f0791a34a46c27f253

Thanks!

      reply	other threads:[~2026-07-20  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  8:41 [PATCH v2] firmware: google: coreboot_table: skip no-map CBMEM entries Hsin-Te Yuan
2026-07-20  2:56 ` Tzung-Bi Shih [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=al2OePSmQNG5zkwx@google.com \
    --to=tzungbi@kernel.org \
    --cc=briannorris@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=jwerner@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yidilin@google.com \
    --cc=yuanhsinte@chromium.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 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.