linux-kernel - Re: [PATCH 6/7 v3] overlay: hybrid overlay filesystem prototype

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: <201009271349.49077.agruen@suse.de>
Date:	Mon, 27 Sep 2010 13:49:48 +0200
From:	Andreas Gruenbacher <agruen@...e.de>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	Valerie Aurora <vaurora@...hat.com>, linuxram@...ibm.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	neilb@...e.de, viro@...iv.linux.org.uk
Subject: Re: [PATCH 6/7 v3] overlay: hybrid overlay filesystem prototype

On Monday 27 September 2010 10:11:53 Miklos Szeredi wrote:
> [...] marking new directories opaque is only a half solution.
> E.g. consider the case when we have /a/b/c/ on the lower fs
> and /a/b/ on the upper, which is not opaque.  Then /a/b/c/ is created
> on the upper fs off-line.  The union logic can't notice that "c"
> should really be opaque and will merge with the contents of the lower
> layer.

I can think of arguments for either behavior, perhaps with a slight preference 
for your suggestion (default = opaque).

In any case, admins will need a way to flip opaque flags and remove undesired 
whiteouts.

Thanks,
Andreas
--
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/