From: Shaya Potter Subject: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem Date: Mon, 04 Sep 2006 09:28:26 -0400 Message-ID: <1157376506.4398.15.camel@localhost.localdomain> References: <20060901013512.GA5788@fsl.cs.sunysb.edu> <20060903110507.GD4884@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Josef Sipek , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, akpm@osdl.org, viro@ftp.linux.org.uk Return-path: Received: from cs.columbia.edu ([128.59.16.20]:14823 "EHLO cs.columbia.edu") by vger.kernel.org with ESMTP id S1751349AbWIDN3o (ORCPT ); Mon, 4 Sep 2006 09:29:44 -0400 To: Pavel Machek In-Reply-To: <20060903110507.GD4884@ucw.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sun, 2006-09-03 at 11:05 +0000, Pavel Machek wrote: > Hi! > > > - Modifying a Unionfs branch directly, while the union is mounted, is > > currently unsupported. Any such change may cause Unionfs to oops and it > > can even result in data loss! > > I'm not sure if that is acceptable. Even root user should be unable to > oops the kernel using 'normal' actions. As I said in the other case. imagine ext2/3 on a a san file system where 2 systems try to make use of it. Will they not have issues?