| 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
| ||
|
Date: Wed, 24 Oct 2012 23:29:10 -0700 From: Kees Cook <keescook@...omium.org> To: Valdis.Kletnieks@...edu Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 000/193] remove CONFIG_EXPERIMENTAL On Wed, Oct 24, 2012 at 6:25 PM, <Valdis.Kletnieks@...edu> wrote: > On Tue, 23 Oct 2012 13:01:13 -0700, Kees Cook said: >> This config item has not carried much meaning for a while now and is >> almost always enabled by default (especially in distro builds). As agreed >> during the Linux kernel summit, it should be removed. >> >> As such, this is the patch series for removing CONFIG_EXPERIMENTAL, >> with the hopes of all the various maintainers pulling these changes into >> their trees. I'm carrying the first patch (that makes CONFIG_EXPERIMENTAL >> "default y") in my linux-next tree, so builds there will see the impact >> immediately. > > Has anybody tested what happens if you're doing a git bisect that ends up crossing > back and forth across the commit for this? I've been burned before when stuff > evaporates out of my .config during a bisect when an option grows/loses a 'depends > on' clause. I haven't tried a bisect, but I've been bouncing around between trees and haven't had any surprises yet. -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/
Powered by blists - more mailing lists