Message-ID: <47C441C1.5060305@garzik.org>
Date: Tue, 26 Feb 2008 11:43:45 -0500
From: Jeff Garzik <jeff@garzik.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Nick Piggin <nickpiggin@yahoo.com.au>
CC: Jamie Lokier <jamie@shareable.org>,
       Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org,
       linux-fsdevel@vger.kernel.org, Chris Wedgwood <cw@f00f.org>
Subject: Re: Proposal for "proper" durable fsync() and fdatasync()
References: <20080226072649.GB30238@shareable.org> <20080225234319.f4589ae4.akpm@linux-foundation.org> <20080226075921.GG30238@shareable.org> <200802262016.11297.nickpiggin@yahoo.com.au>
In-Reply-To: <200802262016.11297.nickpiggin@yahoo.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 631
Lines: 18

Nick Piggin wrote:
> Anyway, the idea of making fsync/fdatasync etc. safe by default is
> a good idea IMO, and is a bad bug that we don't do that :(

Agreed...  it's also disappointing that [unless I'm mistaken] you have 
to hack each filesystem to support barriers.

It seems far easier to make sync_blkdev() Do The Right Thing, and 
magically make all filesystems data-safe.

	Jeff


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