linux-kernel - Re: [2.6 patch] remove 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]

Date:	Tue, 1 Jan 2008 14:30:22 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL

On Tue, 1 Jan 2008 15:26:23 +0100
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Adrian Bunk <bunk@...nel.org> wrote:
> 
> > This patch removes the EXPERIMENTAL option and all dependencies on 
> > EXPERIMENTAL since they are pointless.
> 
> agreed. CONFIG_BROKEN has real use - but CONFIG_EXPERIMENTAL is pretty 
> pointless in the 90-days kernel development model.

Then I need a replacement equivalent for the ATA layer and all the other
drivers using it to indicate stuff that *IS* experimental, or not yet
known to be highly robust. Drivers are not the same as core code Ingo and
the world driver writers live in is very different to the one you operate
in as is clearly shown by this and by the _p discussion.

Still NAK.  As the alternative is

CONFIG_ATA_EXPERIMENTAL, CONFIG_NET_EXPERIMENTAL,
CONFIG_VIDEO_EXPERIMENTAL, ... all being added by developers

We will also need experimental badly in future when the EU liability
rules (and probably the US ones in a similar time scale) change so that
liability applies to software, because then it will be very important to
clearly label code that is experimental or development code as such.

Alan
--
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/