All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>,
	Michal Clapinski <mclapinski@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Chris Li <chrisl@kernel.org>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] x86/boot/compressed: Fix avoiding memmap in physical KASLR
Date: Thu, 6 Nov 2025 08:36:06 -0800	[thread overview]
Message-ID: <6074cbfa-b529-45f5-b696-044464ed433e@intel.com> (raw)
In-Reply-To: <CAMj1kXFc5fcXM1UCtgev+7LFyc+vuTD-M0ma31fNasOGmpQqUQ@mail.gmail.com>

On 11/6/25 08:32, Ard Biesheuvel wrote:
> This looks fine to me, but as I noted before, I'd happily simply
> disable physical KASLR entirely if 'memmap=' appears at all.

Hey, post the patch and we'll see which one looks better.

  reply	other threads:[~2025-11-06 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 16:23 [PATCH v3 1/1] x86/boot/compressed: Fix avoiding memmap in physical KASLR Michal Clapinski
2025-11-06 16:32 ` Ard Biesheuvel
2025-11-06 16:36   ` Dave Hansen [this message]
2025-12-08 13:27     ` Michał Cłapiński
2025-12-09  0:43       ` Borislav Petkov
2025-12-29 14:25         ` Michał Cłapiński
2026-01-08 13:36           ` Ard Biesheuvel
2026-01-12 21:39           ` Borislav Petkov
2026-01-13 11:21             ` Michał Cłapiński
2026-01-13 11:27               ` Borislav Petkov
2026-01-13 11:39                 ` Michał Cłapiński
2026-01-13 11:54                   ` Borislav Petkov
2026-01-13 12:18                     ` Ard Biesheuvel

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=6074cbfa-b529-45f5-b696-044464ed433e@intel.com \
    --to=dave.hansen@intel.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=chrisl@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mclapinski@google.com \
    --cc=mingo@redhat.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.