| 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
| ||
|
Message-ID: <20080111104144.GA31709@linux-sh.org> Date: Fri, 11 Jan 2008 19:41:44 +0900 From: Paul Mundt <lethal@...ux-sh.org> To: Ralf Baechle <ralf@...ux-mips.org> Cc: Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL On Thu, Jan 10, 2008 at 10:18:45PM +0000, Ralf Baechle wrote: > On Tue, Jan 01, 2008 at 03:48:09PM +0200, Adrian Bunk wrote: > > Definately NAK for the MIPS segments. Some of the EXPERIMENTAL > dependencies should be removed but many options tagged with EXPERIMENTAL > are still dangerous. > Likewise for the SH portions. EXPERIMENTAL in these places really does mean EXPERIMENTAL. BROKEN has very different meanings, as does silently promoting the offending options to !EXPERIMENTAL. While EXPERIMENTAL in drivers/ might not have any real meaning, most of the examples listed for arch/ have been intentional, and I'd wager that most arch maintainers used it both carefully and intentionally. There's no reason to punish arch/ for the transgressions of drivers/. If enough subsystems switch off of EXPERIMENTAL and use a subsystem-specific EXPERIMENTAL option, then perhaps we can reclaim EXPERIMENTAL to actually mean what it's supposed to, without worrying about people just turning it on to get at all of their missing driver options. -- 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/
Powered by blists - more mailing lists