From: Kees Cook <kees@kernel.org>
To: Andrew Donnellan <ajd@linux.ibm.com>,
Vegard Nossum <vegard.nossum@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Petr Vorel <pvorel@suse.cz>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] kconfig: Avoid prompting for transitional symbols
Date: Tue, 30 Sep 2025 23:00:07 -0700 [thread overview]
Message-ID: <B1170B95-F9B4-43F5-90A7-B31076CDA3F3@kernel.org> (raw)
In-Reply-To: <01f772073dba88daf7f5acd824d10fc37412c99e.camel@linux.ibm.com>
On September 30, 2025 9:21:07 PM PDT, Andrew Donnellan <ajd@linux.ibm.com> wrote:
>On Tue, 2025-09-30 at 08:45 -0700, Kees Cook wrote:
>> The "transitional" symbol keyword, while working with the "olddefconfig"
>> target, was prompting during "oldconfig". This occurred because these
>> symbols were not being marked as user-defined when they received values
>> from transitional symbols that had user values. The "olddefconfig" target
>> explicitly doesn't prompt for anything, so this deficiency wasn't noticed.
>>
>> The issue manifested when a symbol's value came from a transitional
>> symbol's user value but the receiving symbol wasn't marked with
>> SYMBOL_DEF_USER. Thus the "oldconfig" logic would then prompt for these
>> symbols unnecessarily.
>>
>> Check after value calculation whether a symbol without a user value
>> gets its value from a single transitional symbol that does have a user
>> value. In such cases, mark the receiving symbol as user-defined to
>> prevent prompting.
>>
>> Update regression tests to verify that symbols with transitional defaults
>> are not prompted in "oldconfig", except when conditional defaults evaluate
>> to 'no' and should legitimately be prompted.
>>
>> Build tested with "make testconfig".
>>
>> Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
>> Closes:
>> https://lore.kernel.org/lkml/CAHk-=wgZjUk4Cy2XgNkTrQoO8XCmNUHrTe5D519Fij1POK+3qw@mail.gmail.com/
>> Fixes: 05020835c86e ("kconfig: Add transitional symbol attribute for migration
>> support")
>
>I think this should be f9afce4f32e9.
Indeed. I fixed this before I pushed it to -next; thank you!
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-10-01 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 15:45 Kees Cook
2025-10-01 4:21 ` Andrew Donnellan
2025-10-01 6:00 ` Kees Cook [this message]
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=B1170B95-F9B4-43F5-90A7-B31076CDA3F3@kernel.org \
--to=kees@kernel.org \
--cc=ajd@linux.ibm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=pvorel@suse.cz \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®