[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=1XKdy6VrAPE7xH65nadFzmrBBJWsLw5tYmxNJqFbnYg@mail.gmail.com>
Date: Fri, 29 Aug 2025 00:55:46 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Kees Cook <kees@...nel.org>
Cc: Nathan Chancellor <nathan@...nel.org>, Randy Dunlap <rdunlap@...radead.org>,
Kees Cook <kees@...flux.net>, Peter Zijlstra <peterz@...radead.org>,
Sami Tolvanen <samitolvanen@...gle.com>, Linus Walleij <linus.walleij@...aro.org>,
Mark Rutland <mark.rutland@....com>, Puranjay Mohan <puranjay@...nel.org>,
David Woodhouse <dwmw2@...radead.org>, Jonathan Corbet <corbet@....net>, x86@...nel.org,
linux-doc@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-riscv@...ts.infradead.org,
llvm@...ts.linux.dev, linux-hardening@...r.kernel.org
Subject: Re: [PATCH 5/5] kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI
On Thu, Aug 28, 2025 at 10:32 PM Kees Cook <kees@...nel.org> wrote:
>
> Oh! Keep CFI_CLANG the visible option? Will the later rename work right? I'll give it a try.
Yeah -- whenever we want, we can move everything to the CFI one, and
hopefully many users that enabled it will not see the prompt since
they will already have the value there already.
Kconfig doesn't save the unset value in this case, so some users will
still see the prompt. Which I guess is good for the GCC users, since
for them it is a new possibility after all, that they should consider.
I didn't really test it thoroughly though. Caveat emptor and all that...
Cheers,
Miguel
Powered by blists - more mailing lists