All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, josh.durgin@dreamhost.com,
	morita.kazutaka@gmail.com, tailai.ly@taobao.com,
	qemu-devel@nongnu.org, rjones@redhat.com, stefanha@redhat.com,
	bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] block: change default of .has_zero_init to 0
Date: Thu, 27 Jun 2013 09:12:55 -0600	[thread overview]
Message-ID: <51CC5677.4040200@redhat.com> (raw)
In-Reply-To: <1372341154-3594-1-git-send-email-pl@kamp.de>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

On 06/27/2013 07:52 AM, Peter Lieven wrote:
> .has_zero_init defaults to 1 for all formats and protocols.
> 
> this is a dangerous default since this means that all
> new added drivers need to manually overwrite it to 0 if
> they do not ensure that a device is zero initialized
> after bdrv_create().
> 
> if a driver needs to explicitly set this value to
> 1 its easier to verify the correctness in the review process.
> 
> during review of the existing drivers it turned out
> that ssh and gluster had a wrong default of 1.
> both protocols support host_devices as backend
> which are not by default zero initialized. this
> wrong assumption will lead to possible corruption
> if qemu-img convert is used to write to such a backend.
> 
> a similar problem with the wrong default existed for
> iscsi mose likely because the driver developer did

s/mose/most/

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  parent reply	other threads:[~2013-06-27 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 13:52 [Qemu-devel] [PATCH] block: change default of .has_zero_init to 0 Peter Lieven
2013-06-27 14:53 ` Richard W.M. Jones
2013-06-27 15:12 ` Eric Blake [this message]
2013-06-28  8:06 ` Kevin Wolf
2013-06-28  8:16   ` Peter Lieven
2013-06-28  8:20     ` Kevin Wolf
2013-06-28  8:25       ` Peter Lieven
2013-06-28 10:09         ` Kevin Wolf
2013-06-28 10:11           ` Peter Lieven
2013-06-28 10:21   ` Peter Lieven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CC5677.4040200@redhat.com \
    --to=eblake@redhat.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=josh.durgin@dreamhost.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@gmail.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=tailai.ly@taobao.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.