linux-kernel - Re: wierd new config options

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]

Date:	Thu, 23 Oct 2008 15:16:44 -0400
From:	Lee Schermerhorn <Lee.Schermerhorn@...com>
To:	Christoph Hellwig <hch@....de>
Cc:	linux-kernel@...r.kernel.org, Roland McGrath <roland@...hat.com>
Subject: Re: wierd new config options

On Thu, 2008-10-23 at 20:18 +0200, Christoph Hellwig wrote:
> Why is UNEVICTABLE_LRU and option?  Is there any rason to turn it off or
> is this just to confuse users?

We discussed this back when we first submitted the patches.  I
considered the NONRECLAIMABLE/UNEVICTABLE LRU mechanism to be a wee bit
experimental at the time.  I wasn't sure that all platform that do want
memory management would necessarily also want the unevictable lru.  It's
easier for me to build it with the option and remove it later than vice
versa.  If the consensus of the community is that it should always be
enabled, then I'm fine with removing the option.  

Lee

> 
> CORE_DUMP_DEFAULT_ELF_HEADERS is similarly odd, it turns something on
> that break old userspace, this really really should be a sysctl to turn
> on instead of a config option.

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