mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/configs: update configs in x86_debug.config
Date: Fri, 22 Jul 2022 16:54:16 +0200	[thread overview]
Message-ID: <Ytq6GO0JJcqT2gOw@zn.tnic> (raw)
In-Reply-To: <20220722121815.27535-1-lukas.bulwahn@gmail.com>

On Fri, Jul 22, 2022 at 02:18:15PM +0200, Lukas Bulwahn wrote:
> Commit 4675ff05de2d ("kmemcheck: rip it out") removes kmemcheck and its
> corresponding build config KMEMCHECK.
> 
> Commit 0f620cefd775 ("objtool: Rename "VMLINUX_VALIDATION" ->
> "NOINSTR_VALIDATION"") renamed the debug config option.
> 
> Adjust x86_debug.config to those changes in debug configs.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>  kernel/configs/x86_debug.config | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/kernel/configs/x86_debug.config b/kernel/configs/x86_debug.config
> index dcd86f32f4ed..6fac5b405334 100644
> --- a/kernel/configs/x86_debug.config
> +++ b/kernel/configs/x86_debug.config
> @@ -7,12 +7,11 @@ CONFIG_DEBUG_SLAB=y
>  CONFIG_DEBUG_KMEMLEAK=y
>  CONFIG_DEBUG_PAGEALLOC=y
>  CONFIG_SLUB_DEBUG_ON=y
> -CONFIG_KMEMCHECK=y

While at it, you might also whack the last mention of KMEMCHECK:

$ git grep KMEMCHECK
kernel/configs/x86_debug.config:10:CONFIG_KMEMCHECK=y
tools/testing/selftests/wireguard/qemu/debug.config:21:CONFIG_HAVE_ARCH_KMEMCHECK=y

Thx.

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2022-07-22 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 12:18 Lukas Bulwahn
2022-07-22 14:54 ` Borislav Petkov [this message]
2022-07-27  4:50   ` Lukas Bulwahn
2022-07-28 10:36 ` [tip: x86/urgent] x86/configs: Update " tip-bot2 for Lukas Bulwahn

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=Ytq6GO0JJcqT2gOw@zn.tnic \
    --to=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --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®