From mboxrd@z Thu Jan  1 00:00:00 1970
From: Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
Date: Sun, 18 Jun 2006 19:36:16 +0100
Message-ID: <20060618183616.GA27946@ftp.linux.org.uk>
References: <20060616231213.D4C5D6AF@localhost.localdomain> <20060616231228.2107A2EE@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	herbert@13thfloor.at
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeniv.linux.org.uk ([195.92.253.2]:3772 "EHLO
	ZenIV.linux.org.uk") by vger.kernel.org with ESMTP id S1751217AbWFRSgR
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Sun, 18 Jun 2006 14:36:17 -0400
To: Dave Hansen <haveblue@us.ibm.com>
Content-Disposition: inline
In-Reply-To: <20060616231228.2107A2EE@localhost.localdomain>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Fri, Jun 16, 2006 at 04:12:28PM -0700, Dave Hansen wrote:
> 
> Originally from: Herbert Poetzl <herbert@13thfloor.at>
> 
> This is the core of the read-only bind mount patch set.
> 
> Note that this does _not_ add a "ro" option directly to
> the bind mount operation.  If you require such a mount,
> you must first do the bind, then follow it up with a
> 'mount -o remount,ro' operation.

Hrm...  So you want r/o status of vfsmount completely independent from
that of superblock?  I.e. allow writable vfsmount over r/o filesystem?
I realize that we have double checks, but...