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: <E1LElCn-0005gp-G1@pomaz-ex.szeredi.hu>
Date:	Mon, 22 Dec 2008 14:52:21 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	raven@...maw.net
CC:	miklos@...redi.hu, linux-fsdevel@...r.kernel.org, jblunck@...e.de,
	dlezcano@...ibm.com, linux-kernel@...r.kernel.org,
	bharata@...ux.vnet.ibm.com, viro@...IV.linux.org.uk,
	vaurora@...hat.com
Subject: Re: [rfc git patch] union directory

On Fri, 19 Dec 2008, Ian Kent wrote:
> Whether the VFS is implementing readdir for a mount's top level or also
> for deeper levels it still has the issue described by Barata Rao in
> http://marc.info/?l=linux-fsdevel&m=118914402631822&w=2. But my
> suggestion doesn't only relate to the readdir issue it implies managing
> such things as whiteout persistence also, but outside of individual file
> systems. So, yes, I'm a bit off topic but the patch series here is going
> to need something like this somewhere to ultimately be useful and all
> I'm saying is that somewhere probably shouldn't be within individual
> file systems and, yes, not in the VFS.

I kind of agree.  I think that adding whiteout (and other bits) to
filesystems to support union{fs,mount} is kludgey.

But I don't agree that union mounts are useless without whiteouts.
Yes, file creation and removal will have unusual semantics, and that
might exclude some (maybe the majority) of uses, but definitely not
all.

> Valerie Henson is planning to start a project (when she is done with
> current commitments) along the lines of a lightweight stacking layer
> with union support included in the file system. These continuing
> individual efforts are a little disjoint so such a project could be an
> ideal way to define what's needed, what the issues are and how it will
> be done in one place. Hopefully everyone that is keen to see progress in
> this area will want to be involved too, ;)

Interesting.

It maybe worth mentioning here that fuse is also a very capable
"stacking layer" and with planned performance improvements it might
become the best option to implement such fs stacks.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ