Date: Thu, 3 Aug 2006 15:39:53 +0100
From: Christoph Hellwig <hch@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, viro@ftp.linux.org.uk, herbert@13thfloor.at,
       hch@infradead.org
Subject: Re: [PATCH 06/28] reintroduce list of vfsmounts over superblock
Message-ID: <20060803143953.GD920@infradead.org>
Mail-Followup-To: Christoph Hellwig <hch@infradead.org>,
	Dave Hansen <haveblue@us.ibm.com>, linux-kernel@vger.kernel.org,
	viro@ftp.linux.org.uk, herbert@13thfloor.at
References: <20060801235240.82ADCA42@localhost.localdomain> <20060801235244.964B79E7@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060801235244.964B79E7@localhost.localdomain>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 914
Lines: 21

On Tue, Aug 01, 2006 at 04:52:44PM -0700, Dave Hansen wrote:
> 
> We're moving a big chunk of the burden of keeping people from
> writing to r/o filesystems from the superblock into the
> vfsmount.  This requires that we consult the superblock's
> vfsmounts when things like remounts occur.
> 
> So, introduce a list of vfsmounts hanging off the superblock.
> We'll use this in a bit.

I don't think we'll need it.  We really need to keep is someone writing
to this vfsmount counters in addition to is someone writing to this sb.

In fact there are cases were we want a superblock to be writeable to
without any view into it being writeable, e.g. for journal recovery.

-
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/