All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.9?] block/io: Comment out permission assertions
Date: Tue, 11 Apr 2017 16:52:21 +0200	[thread overview]
Message-ID: <97a7574e-4c00-62bb-e154-a4085b6243e0@redhat.com> (raw)
In-Reply-To: <20170411145050.31290-1-mreitz@redhat.com>

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

On 11.04.2017 16:50, Max Reitz wrote:
> In case of block migration, there may be writes to BlockBackends that do
> not have the write permission taken. Before this issue is fixed (which
> is not going to happen in 2.9), we therefore cannot assert that this is
> the case.
> 
> Suggested-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
>  block.c    |  6 +++++-
>  block/io.c | 12 ++++++++++--
>  2 files changed, 15 insertions(+), 3 deletions(-)

I'll send a revert for 2.10 if/when this is merged.

Max


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

  reply	other threads:[~2017-04-11 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 14:50 [Qemu-devel] [PATCH for-2.9?] block/io: Comment out permission assertions Max Reitz
2017-04-11 14:52 ` Max Reitz [this message]
2017-04-11 14:58 ` Kevin Wolf
2017-04-11 15:07   ` Laurent Vivier
2017-04-12 13:18     ` Kevin Wolf
2017-04-12 13:28       ` Laurent Vivier
2017-04-11 15:47 ` Peter Maydell

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=97a7574e-4c00-62bb-e154-a4085b6243e0@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.