Date: Tue, 5 Aug 2003 17:59:24 +0100
From: viro@parcelfarce.linux.theplanet.co.uk
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
       Christoph Hellwig <hch@infradead.org>
Subject: Re: RO --bind mount implementation ...
Message-ID: <20030805165924.GF12757@parcelfarce.linux.theplanet.co.uk>
References: <20030804221615.GA18521@www.13thfloor.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20030804221615.GA18521@www.13thfloor.at>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 847
Lines: 19

On Tue, Aug 05, 2003 at 12:16:15AM +0200, Herbert P?tzl wrote:
 
> anyway, I discussed this with some friends, and
> they pointed out that this would be useful ...
> so here is the first try ...

Umm...  You know, the most obvious system call that should care about
read-only is open(pathname, O_RDWR) ;-)  IOW, taking care of directory
modifications is not enough - you need to deal with
	* opening file for write
	* truncation (both from *truncate() and from open() with O_TRUNC)
	* metadata changes (timestamps, ownership, permissions)

But yes, it's not that far from where we should eventualy get.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/