All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Simon Horman <horms@kernel.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Borislav Petkov <bp@suse.de>,
	Nicolas Schier <nicolas.schier@linux.dev>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Joel Fernandes (Google)" <joel@joelfernandes.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] configs/debug: Refresh debug config dependencies
Date: Tue, 22 Apr 2025 19:15:44 +0200	[thread overview]
Message-ID: <a115518c-c21d-4e0f-8abf-a1732031a760@kernel.org> (raw)
In-Reply-To: <20250422165446.work.015-kees@kernel.org>

Hi Kees,

Thank you for sharing this patch!

On 22/04/2025 18:54, Kees Cook wrote:
> Many of the CONFIG_DEBUG* options need CONFIG_DEBUG_KERNEL=y to be set,

Good point! I guess it has not been seen before because it is usually
enabled in the different _defconfig files. So probably no need to
backport this I guess, right?


> so enable it explicitly. Similarly for CONFIG_NET* options, enable
> CONFIG_NET=y.

I'm not sure about that one: if I'm not mistaken, the net debugging
options have been added for CIs using network features, to find bugs in
this area. In other words, I don't think it is needed to add a
dependence to CONFIG_NET. If it is enabled, then some extra debugging
options should be enabled to get more debug. If not, no need to force
having CONFIG_NET, no?

(On the other hand, CONFIG_NET is very likely needed for a CI, and it is
typically enabled in the different _defconfig and kvm_guest.config. I
guess adding this dependence will very likely not annoy anybody, so up
to you :) )


> Finally, remove CONFIG_DEBUG_VM_VMACACHE, since it was
> removed in commit 7964cf8caa4d ("mm: remove vmacache").

Good catch!

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-04-22 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 16:54 [PATCH] configs/debug: Refresh debug config dependencies Kees Cook
2025-04-22 17:15 ` Matthieu Baerts [this message]
2025-04-22 17:52   ` Kees Cook

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=a115518c-c21d-4e0f-8abf-a1732031a760@kernel.org \
    --to=matttbe@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=bp@suse.de \
    --cc=horms@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=masahiroy@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=nicolas.schier@linux.dev \
    --cc=sdf@fomichev.me \
    /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.