linux-kernel - Re: New filesystem for Linux kernel

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]

Message-ID: <37786d4b0902260631r4916b5a8h93700257d882c233@mail.gmail.com>
Date:	Thu, 26 Feb 2009 16:31:39 +0200
From:	Amit Kucheria <amit.kucheria@...durent.com>
To:	Theodore Tso <tytso@....edu>, Tomas M <tomas@...x.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux kernel

On Tue, Feb 24, 2009 at 4:15 PM, Theodore Tso <tytso@....edu> wrote:
> On Tue, Feb 24, 2009 at 09:13:08AM +0100, Tomas M wrote:
>> An overview of aufs2 has been submitted to this list.
>> I noticed zero response at all. Nobody cares?
>>
>> I suggest to remove unionfs from Andrew's -mm tree and replace it by aufs2!
>> Tell me why this should not happen...
>
> Um, you need to tell us why aufs2 is better than Unionfs.  The burden
> of proof rests on your shoulders.  The code which is displacing
> existing code needs to give a justification about why it is better
> than the code which is displacing, not the other way around.

Does it really have to displace unionfs? Why can't it be merged in
(after proper review) alongside unionfs?

Ubuntu moved to aufs for some of the same reasons that Tomas has
outlined elsewhere in this thread. Unionfs required some hand holding
everytime we upgraded to a new kernel while aufs has not given us
those problems. And yes, unionfs races have given us several sleepless
nights before releases.

Regards,
Amit (with Ubuntu Kernel Developer hat on)
--
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/