Date: Sun, 18 Apr 2004 10:17:00 +0200
From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] lockfs - vfs bits
Message-ID: <20040418081659.GA8972@lst.de>
Mail-Followup-To: Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
References: <20040417220632.GA2573@lst.de> <20040417163007.67d23c10.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040417163007.67d23c10.akpm@osdl.org>
User-Agent: Mutt/1.3.28i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1066
Lines: 23

On Sat, Apr 17, 2004 at 04:30:07PM -0700, Andrew Morton wrote:
> Christoph Hellwig <hch@lst.de> wrote:
> >
> >  These are the generic lockfs bits.  Basically it takes the XFS freezing
> >  statemachine into the VFS.  It's all behind the kernel-doc documented
> >  freeze_bdev and thaw_bdev interfaces.
> 
> Do we expect to see snapshotting patches for other filesystems arise as a
> result of this?

Other filesystems already implement the write_super_lockfs and unlockfs
methods and should just work.  An earlier version of this patch is in
SuSE's tree and I think they've tested it with ext3 and reiserfs.
Similarly even earlier variants are in the 2.4 vendor trees.  Those
filesystem don't really use the state machine to avoid starting new
transactions, so to get results as reliable as XFS they need soem more
work.

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