[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110616112230.GD26110@elte.hu>
Date: Thu, 16 Jun 2011 13:22:30 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Christoph Hellwig <hch@...radead.org>
Cc: Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Alexander Graf <agraf@...e.de>,
Prasad Joshi <prasadjoshi124@...il.com>,
Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Sasha Levin <levinsasha928@...il.com>,
Cyrill Gorcunov <gorcunov@...il.com>,
Asias He <asias.hejun@...il.com>,
Jens Axboe <jaxboe@...ionio.com>
Subject: Re: [ANNOUNCE] Native Linux KVM tool v2
* Christoph Hellwig <hch@...radead.org> wrote:
> On Thu, Jun 16, 2011 at 12:57:36PM +0300, Pekka Enberg wrote:
> > Uh-oh. Someone needs to apply this patch to sync_file_range():
>
> There actually are a few cases where using it makes sense. [...]
Such as? I don't think apps can actually know whether disk blocks
have been 'instantiated' by a particular filesystem or not, so the
manpage:
Some details
None of these operations write out the file’s metadata. Therefore, unless the appli-
cation is strictly performing overwrites of already-instantiated disk blocks, there
are no guarantees that the data will be available after a crash.
is rather misleading. This is a dangerous (and rather pointless)
syscall and this should be made much clearer in the manpage.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists