From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40808)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1bxEAu-0005sK-RT
	for qemu-devel@nongnu.org; Thu, 20 Oct 2016 10:18:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1bxEAq-0007rg-GD
	for qemu-devel@nongnu.org; Thu, 20 Oct 2016 10:18:28 -0400
Received: from mx1.redhat.com ([209.132.183.28]:38786)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <imammedo@redhat.com>) id 1bxEAq-0007rX-AY
	for qemu-devel@nongnu.org; Thu, 20 Oct 2016 10:18:24 -0400
Date: Thu, 20 Oct 2016 16:18:20 +0200
From: Igor Mammedov <imammedo@redhat.com>
Message-ID: <20161020161820.3bcfce3a@nial.brq.redhat.com>
In-Reply-To: <20161020135711.GZ5057@thinpad.lan.raisama.net>
References: <20161020061301.31372-1-haozhong.zhang@intel.com>
	<20161020143412.5ea6b564@nial.brq.redhat.com>
	<20161020132159.GU5057@thinpad.lan.raisama.net>
	<20161020133353.qfscowwx5bldzvdc@hz-desktop>
	<20161020154732.5f0a87a8@nial.brq.redhat.com>
	<20161020135711.GZ5057@thinpad.lan.raisama.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] hostmem-file: add a property 'notrunc' to
 avoid data corruption
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Haozhong Zhang <haozhong.zhang@intel.com>, qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>, Peter Crosthwaite <crosthwaite.peter@gmail.com>, Richard Henderson <rth@twiddle.net>, Xiao Guangrong <guangrong.xiao@linux.intel.com>, kwolf@redhat.com, mreitz@redhat.com

On Thu, 20 Oct 2016 11:57:11 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:

> On Thu, Oct 20, 2016 at 03:47:32PM +0200, Igor Mammedov wrote:
> > On Thu, 20 Oct 2016 21:33:53 +0800
> > Haozhong Zhang <haozhong.zhang@intel.com> wrote:
> >   
> > > On 10/20/16 11:21 -0200, Eduardo Habkost wrote:  
> > > >On Thu, Oct 20, 2016 at 02:34:12PM +0200, Igor Mammedov wrote:    
> > > >> On Thu, 20 Oct 2016 14:13:01 +0800
> > > >> Haozhong Zhang <haozhong.zhang@intel.com> wrote:
> > > >>    
> > > >> > If a file is used as the backend of memory-backend-file and its size is
> > > >> > not identical to the property 'size', the file will be truncated. For a
> > > >> > file used as the backend of vNVDIMM, its data is expected to be
> > > >> > persistent and the truncation may corrupt the existing data.    
> > > >> I wonder if it's possible just skip 'size' property in your case instead
> > > >> 'notrunc' property. That way if size is not present one'd get actual size
> > > >> using get_file_size() and set 'size' to it?
> > > >> And if 'size' is provided and 'size' != file_size then error out.    
> > > >
> > > >I think it is valid to start with a zero-size file and then let
> > > >QEMU extend it.    
> > > 
> > > For vNVDIMM, extending from zero-size file can be valid when a file is
> > > first used. However, it's not valid for the second and following use
> > > of the same file.  
> > I'd avoid 0 sized backend files and enforce non 0 size value
> > with exact match to actual file size. i.e. let mgmt side take care of
> > proper backend file allocation.  
> 
> This would break compatibility with existing setups that rely on
> the ftruncate() behavior.

Question is what exactly rely on truncate behavior?