linux-kernel - Re: [PATCH] x86: make config X86_FEATURE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c0dcbda3-e131-2460-4c61-e98d0be750ff@intel.com>
Date:   Tue, 9 May 2023 11:43:12 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H . Peter Anvin" <hpa@...or.com>, kernel-janitors@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: make config X86_FEATURE_NAMES visible with EXPERT

On 5/9/23 11:41, Borislav Petkov wrote:
> On Tue, May 09, 2023 at 11:38:27AM -0700, Dave Hansen wrote:
>> This actually isn't _great_ for x86.  We hid X86_FEATURE_NAMES behind
>> EMBEDDED because we didn't want to see it 99% of the time.  But just
>> about everyone uses EXPERT=y, so the end result here is that everyone
>> will now see X86_FEATURE_NAMES.
>>
>> Oh well.  It's just one Kconfig option.  Not a big deal.
> Or we can make it unconditional. I haven't heard anything from the tiny
> .config folks in a while and a !X86_FEATURE_NAMES kernel is just
> unfriendly.

Like remove the option entirely?  Or just remove the prompt so folks
have to hack the .config for it?