mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86/Kconfig: Disable KASLR on debug builds
Date: Thu, 30 Nov 2023 13:49:09 +0100	[thread overview]
Message-ID: <20231130124909.GEZWiExTP4J1pjNxPq@fat_crate.local> (raw)
In-Reply-To: <20231130120831.GB20153@noisy.programming.kicks-ass.net>

On Thu, Nov 30, 2023 at 01:08:31PM +0100, Peter Zijlstra wrote:
> Works for me, but I have "nokaslr no_hash_pointers" on all my machines
> by now. It goes right along with "debug ignore_loglevel
> sysrq_always_enabled earlyprintk=serial,ttyS0,115200" :-)

Bah, there's cmdline switches. Lemme add them to all my scripts starting
guests and grub too. Thanks for the hint!

I guess we could still do the Kconfig dependency when we're on new
machines, without the scripts.

Btw, I'm not the only one who's walked right into this one:

config KCOV
        bool "Code coverage for fuzzing"

	...

          If RANDOMIZE_BASE is enabled, PC values will not be stable across
          different machines and across reboots. If you need stable PC values,
          disable RANDOMIZE_BASE.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2023-11-30 12:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 12:05 Borislav Petkov
2023-11-30 12:08 ` Peter Zijlstra
2023-11-30 12:49   ` Borislav Petkov [this message]
2023-12-04 10:42     ` Mark Rutland
2023-12-04 15:49       ` Borislav Petkov
2023-12-04 17:20         ` Mark Rutland
2023-11-30 18:10 ` Nathan Chancellor
2023-11-30 19:34   ` Borislav Petkov
2023-12-01 16:16     ` Nathan Chancellor
2023-12-01 16:24       ` Borislav Petkov
2023-12-01 16:58         ` Nathan Chancellor

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=20231130124909.GEZWiExTP4J1pjNxPq@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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 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®