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  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]
Date:	Mon, 10 Nov 2014 12:08:13 -0500
From:	Erez Zadok <ezk@....cs.sunysb.edu>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	Jordi Pujol Palomer <jordipujolp@...il.com>,
	linux-unionfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>,
	Al Viro <viro@...iv.linux.org.uk>, "A. Wan" <jm@...wan.com>,
	Patrick Frisch <patrick@...schux.de>,
	Aaron Campbell <aaron@...or.net>
Subject: Re: [RFC PATCH] overlayfs: support more than one read-only layer

Indeed, Miklos, changing layers dynamically is VERY tricky.  Unionfs supports that, but a good amount of its code all over is dedicated to handling dynamic layer changes.  I advise you to avoid supporting this feature for a while, if ever: get a small, functional, working overlayfs first.

I personally never liked the idea of changing layers dynamically: it’s like asking a file system to remain consistent and detect all lower changes when someone goes and hand-edits disk blocks.  Too messy.  The pain of developing and supporting such a feature is much greater than the annoyance to users who have to unmount and remount back their layers to form a new structure.

Cheers,
Erez.

> On Nov 10, 2014, at 4:09 AM, Miklos Szeredi <miklos@...redi.hu> wrote:
> 
> As for changing the stacking while the overlayfs is mounted: currently this is
> not supported, the layers specified at the mount time remain there until the
> overlay is unmounted.  Currently there's no possibility to add or remove layers
> in a dynamic way, and it is definitely more tricky to implement than the static
> configuration.
> 
> 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