From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH 8/9] overlay: overlay filesystem documentation Date: Wed, 13 Mar 2013 16:06:23 -0700 Message-ID: <20130313160623.52ec76cd5239c791b59828b8@linux-foundation.org> References: <1363184193-1796-1-git-send-email-miklos@szeredi.hu> <1363184193-1796-9-git-send-email-miklos@szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, hch@infradead.org, apw@canonical.com, nbd@openwrt.org, neilb@suse.de, jordipujolp@gmail.com, ezk@fsl.cs.sunysb.edu, dhowells@redhat.com, sedat.dilek@googlemail.com, hooanon05@yahoo.co.jp, mszeredi@suse.cz To: Miklos Szeredi Return-path: Received: from mail.linuxfoundation.org ([140.211.169.12]:53038 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755559Ab3CMXG0 (ORCPT ); Wed, 13 Mar 2013 19:06:26 -0400 In-Reply-To: <1363184193-1796-9-git-send-email-miklos@szeredi.hu> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 13 Mar 2013 15:16:32 +0100 Miklos Szeredi wrote: > From: Neil Brown > > Document the overlay filesystem. > Damn, I did it again. This is good, thanks. > +Changes to the underlying filesystems while part of a mounted overlay > +filesystem are not allowed. If the underlying filesystem is changed, > +the behavior of the overlay is undefined, though it will not result in > +a crash or deadlock. ah-hah, there it is. I was wondering how this can-o-worms would be handled ;) Is there anything in place to enforce this at runtime? Checks for read-onlyness, code to prevent rw remounts, etc?