From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Nir Lichtman <nir_lichtman@hotmail.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"luto@kernel.org" <luto@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"m.younesbadr@gmail.com" <m.younesbadr@gmail.com>,
Nir Lichtman <nir@lichtman.org>
Subject: Re: [PATCH v2 RESEND] x86/kaslr: Ingest nokaslr to avoid passing it to init process
Date: Tue, 14 Jan 2025 15:09:54 +0100 [thread overview]
Message-ID: <20250114140954.GR5388@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250114123142.GCZ4ZZLiIBm2cMg9ny@fat_crate.local>
On Tue, Jan 14, 2025 at 01:31:42PM +0100, Borislav Petkov wrote:
> On Tue, Jan 14, 2025 at 10:36:43AM +0100, Peter Zijlstra wrote:
> > On Sat, Jan 11, 2025 at 02:17:43PM +0000, Nir Lichtman wrote:
> > > Problem: Currently booting the kernel with "nokaslr" on x86 incorrectly
> > > doesn't recognize this parameter and passes it on to the init process
> >
> > What now? I'm pretty sure nokaslr works, it's in all my test machines
> > and qemu scripts. Without it faddr2line wouldn't work, which I would
> > notice in a hurry.
>
> Yeah, the param itself works - he doesn't want to pass it on to the init
> process because then it says:
>
> [ 0.073613] Unknown kernel command line parameters "nokaslr", will be passed to user space.
>
> due to our detection of which parameters got eaten and which didn't.
I had never noticed; random machine of mine says:
[ 0.591565] Unknown kernel command line parameters "force_early_printk nokaslr kgdboc=ttyS0", will be passed to user space.
*shrug*, who cares.
next prev parent reply other threads:[~2025-01-14 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 14:17 Nir Lichtman
2025-01-14 9:36 ` Peter Zijlstra
2025-01-14 12:31 ` Borislav Petkov
2025-01-14 14:09 ` Peter Zijlstra [this message]
2025-01-14 14:37 ` Nir Lichtman
2025-01-14 14:55 ` Borislav Petkov
2025-01-14 15:02 ` Nir Lichtman
2025-01-14 20:30 ` Borislav Petkov
2025-01-14 22:29 ` Nir Lichtman
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=20250114140954.GR5388@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=m.younesbadr@gmail.com \
--cc=mingo@redhat.com \
--cc=nir@lichtman.org \
--cc=nir_lichtman@hotmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®