From: Kees Cook <kees@kernel.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <masahiroy@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Stephen Brennan <stephen.s.brennan@oracle.com>,
Marco Bonelli <marco@mebeim.net>, Petr Vorel <pvorel@suse.cz>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] kconfig: Add transitional symbol attribute for migration support
Date: Fri, 5 Sep 2025 09:23:55 -0700 [thread overview]
Message-ID: <202509050921.2398728EE2@keescook> (raw)
In-Reply-To: <4cbc348d-02ca-4743-b8d4-21db2ebf4460@oracle.com>
On Thu, Sep 04, 2025 at 07:03:56PM +0200, Vegard Nossum wrote:
>
> On 04/09/2025 04:51, Kees Cook wrote:
> > On Mon, Sep 01, 2025 at 08:44:56PM +0200, Vegard Nossum wrote:
> > > If you change sym_calc_visibility() to always return 'yes' for
> > > transitional values then I don't think you need to touch
> > > sym_calc_value() at all.
> >
> > Hm, it looks like sym_calc_visibility() doesn't strictly just look at
> > visibility. And visibility seems to "last"? And I think the "tri" still
> > can't just be "yes", don't we need the other stuff handled?
> >
> > Do you see a way to do it how you're suggesting? And now I wrote the
> > regression tests so we can test any alternatives! ;)
>
> Here's what I had in mind (on top of your kcfi patchset), see the
> attachment.
>
> It basically undoes all your additions to sym_calc_value() in favour of
> two straightforward additions:
>
> @@ -214,6 +214,11 @@ static void sym_calc_visibility(struct symbol *sym)
> struct property *prop;
> tristate tri;
>
> + if (sym->flags & SYMBOL_HIDDEN) {
> + sym->visible = yes;
> + return;
> + }
> +
If this doesn't break "m" choices and the config doesn't show up in
menuconfig, then yeah, I can do this.
I'll give it a spin!
--
Kees Cook
next prev parent reply other threads:[~2025-09-05 16:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 2:01 [PATCH v2] kconfig: Add transitional symbol attribute for migration support Kees Cook
2025-09-01 8:34 ` Vegard Nossum
2025-09-01 16:56 ` Kees Cook
2025-09-01 18:20 ` Vegard Nossum
2025-09-01 18:31 ` Kees Cook
2025-09-01 18:44 ` Vegard Nossum
2025-09-04 2:51 ` Kees Cook
2025-09-04 17:03 ` Vegard Nossum
2025-09-04 17:10 ` Vegard Nossum
2025-09-05 9:41 ` Vegard Nossum
2025-09-05 16:24 ` Kees Cook
2025-09-05 16:23 ` Kees Cook [this message]
2025-09-01 9:09 ` Jani Nikula
2025-09-01 16:48 ` Kees Cook
2025-09-01 16:39 ` Randy Dunlap
2025-09-01 16:45 ` Kees Cook
2025-09-01 16:54 ` Randy Dunlap
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=202509050921.2398728EE2@keescook \
--to=kees@kernel.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@mebeim.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=ojeda@kernel.org \
--cc=pvorel@suse.cz \
--cc=rdunlap@infradead.org \
--cc=stephen.s.brennan@oracle.com \
--cc=vegard.nossum@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).