linux-ext4 - Re: what exactly is CONFIG_EXT4_USE_FOR

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] [day] [month] [year] [list]

Message-ID: <4B995629.6020402@redhat.com>
Date:	Thu, 11 Mar 2010 14:44:25 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	tytso@....edu
CC:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: what exactly is CONFIG_EXT4_USE_FOR_EXT23 for?

tytso@....edu wrote:
> On Thu, Mar 11, 2010 at 01:54:42PM -0600, Eric Sandeen wrote:
>> As long as it doesn't contaminate the "core" then sure, but the more twisty
>> paths we have, the less likely any of them will be maintainable.  :)
>>
>> I just think that before adding more knobs, we need to take a long hard
>> look at what it does to the big picture.  When documenting ext4 upstream,
>> how many "if ... else if ... else if" clauses do we need?
> 
> Fair enough.
> 
> I'm all for proposals to get rid of some knobs, too, if we don't think
> they serve a purpose.  Recent examples that we've started deprecated
> include minixdf --- and I really wonder if we need t have explicit
> mount options to enable xattr and acl's.  Anyone object if we just
> enable them all the time by default?
> 
>               	    	    	    - Ted

I'd be happy with that.  It always bites me when I forget ;)

Do we still need auto_da_alloc as a disable-able option?

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html