linux-kernel - Re: [PATCH 002/193] checkpatch: warn about using CONFIG

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAGXu5jLh0Y69G5ZA1W9A_2aVGoGcEgkcV0HUV5HyocLQKNvssg@mail.gmail.com>
Date:	Tue, 23 Oct 2012 16:18:52 -0700
From:	Kees Cook <keescook@...omium.org>
To:	Andy Whitcroft <apw@...onical.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 002/193] checkpatch: warn about using CONFIG_EXPERIMENTAL

On Tue, Oct 23, 2012 at 3:59 PM, Andy Whitcroft <apw@...onical.com> wrote:
> On Tue, Oct 23, 2012 at 01:01:15PM -0700, Kees Cook wrote:
>> This config item has not carried much meaning for a while now and is
>> almost always enabled by default. As agreed during the Linux kernel
>> summit, it is being removed.  This will discourage future addition of
>> CONFIG_EXPERIMENTAL while it is being phased out.
>>
>> Cc: Andy Whitcroft <apw@...onical.com>
>> Signed-off-by: Kees Cook <keescook@...omium.org>
>> ---
>>  scripts/checkpatch.pl |    7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index 21a9f5d..37dc932 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -1757,6 +1757,13 @@ sub process {
>>                       #print "is_start<$is_start> is_end<$is_end> length<$length>\n";
>>               }
>>
>> +# Discourage the addition of CONFIG_EXPERIMENTAL in Kconfig.
>> +             if ($realfile =~ /Kconfig/ &&
>> +                 $line =~ /.\s*depends on\s+.*\bEXPERIMENTAL\b/) {
>> +                     WARN("CONFIG_EXPERIMENTAL",
>> +                          "Use of CONFIG_EXPERIMENTAL is deprecated.\n");
>> +             }
>> +
>
> Seem reasonable.  Should you suggest how they can mark things
> experimental?  I assume (EXPERIMENTAL) in the title is now the right
> way?

Yeah, there's an escalation that seemed to get agreed on:
https://lkml.org/lkml/2012/10/23/580

I could add a hint to read the above lkml post?

-Kees

-- 
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/