| 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
| ||
|
Message-ID: <CAJfpegtRktN8BdOogCMW++Gar02j06K=9OYOyDMBbwBZq6_=Hg@mail.gmail.com> Date: Fri, 21 Nov 2014 13:41:57 +0100 From: Miklos Szeredi <miklos@...redi.hu> To: Hans-Peter Jansen <hpj@...la.net> Cc: Al Viro <viro@...iv.linux.org.uk>, Linus Torvalds <torvalds@...ux-foundation.org>, Linux-Fsdevel <linux-fsdevel@...r.kernel.org>, Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-unionfs@...r.kernel.org Subject: Re: [GIT PULL] overlay filesystem fixes for 3.18 On Fri, Nov 21, 2014 at 12:32 PM, Hans-Peter Jansen <hpj@...la.net> wrote: > 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? See this thread: https://lkml.org/lkml/2014/11/18/433 Thanks, Miklos -- 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