linux-kernel - Re: [GIT PULL] overlay filesystem fixes for 3.18

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: <1962959.JkOx4gJGaG@xrated>
Date:	Fri, 21 Nov 2014 12:32:54 +0100
From:	Hans-Peter Jansen <hpj@...la.net>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	Al Viro <viro@...iv.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-unionfs@...r.kernel.org
Subject: Re: [GIT PULL] overlay filesystem fixes for 3.18

Dear Miklos,

On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote:
> 
> The biggest change is to rename the filesystem from "overlayfs" to
> "overlay". This will allow legacy overlayfs to be easily carried by distros
> alongside the new mainline one.

Would you kindly give a firm elaboration of this rename? 

Why would a distro kernel maintainer want to keep the external overlayfs 
patches together with the now in kernel module?

Isn't it enough to drop the external patches from distro kernels in order to 
use it successfully or are there any semantic changes hidden that an admin 
should know about?

BTW: congrats to all involved parties. A layered filesystem finally arrived in 
the Linux kernel! This is a quantum leap for creative system architects.

Cheers,
Pete

proud user of aufs (and formerly unionfs) based fat diskless systems since 
about a decade.
--
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/