[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140213162534.GB4026@tucsk.piliscsaba.szeredi.hu>
Date: Thu, 13 Feb 2014 17:25:34 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: David Howells <dhowells@...hat.com>
Cc: viro@...IV.linux.org.uk, torvalds@...ux-foundation.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
bfields@...ldses.org, hch@...radead.org, akpm@...ux-foundation.org,
zab@...hat.com, jack@...e.cz, luto@...capital.net, mszeredi@...e.cz
Subject: Re: [PATCH 00/13] cross rename v4
On Thu, Feb 13, 2014 at 03:54:14PM +0000, David Howells wrote:
>
> If we're going to be adding a new rename inode op, can we make it take a flag
> to white out the source for union type things? This would mean that
> rename-and-white-out can be done atomically.
That is an option, yes.
Regarding whiteouts, I raised a couple of questions that nobody answered yet, so
let me ask again.
- If a filesystem containing whiteouts (fallthroughs, etc...) is mounted as not
part of a union, how are these special entities represented to userspace?
- Can the user remove them?
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