From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.10] Revert "block/io: Comment out permission assertions"
Date: Thu, 13 Apr 2017 16:34:24 +0200 [thread overview]
Message-ID: <50cc7a90-607a-f10e-f1d8-403e8fe75d77@redhat.com> (raw)
In-Reply-To: <20170413132825.GB13387@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On 13.04.2017 15:28, Stefan Hajnoczi wrote:
> On Tue, Apr 11, 2017 at 05:52:26PM +0200, Max Reitz wrote:
>> This reverts commit e3e0003a8f6570aba1421ef99a0b383a43371a74.
>>
>> This commit was necessary for the 2.9 release because we were unable to
>> fix the underlying issue(s) in time. However, we will be for 2.10.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> block.c | 6 +-----
>> block/io.c | 12 ++----------
>> 2 files changed, 3 insertions(+), 15 deletions(-)
>
> Should we merge a fix before enabling the assertion again? It's a known
> issue. Let people using qemu.git live a little and have fun without the
> inevitable SIGABRT coredumps. We don't benefit if more people encounter
> this crash and duplicate work debugging it.
Yes, we should probably merge the fixes we know about before. But after
that, I'd rather merge this patch as soon as possible so we do have a
chance of getting more reports (if anything else is broken) before the
next freeze. :-)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-04-13 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 15:52 [Qemu-devel] [PATCH for-2.10] Revert "block/io: Comment out permission assertions" Max Reitz
2017-04-11 16:32 ` Fam Zheng
2017-04-13 13:28 ` Stefan Hajnoczi
2017-04-13 14:34 ` Max Reitz [this message]
2017-04-14 1:10 ` [Qemu-devel] [Qemu-block] " John Snow
2017-04-14 6:46 ` Stefan Hajnoczi
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=50cc7a90-607a-f10e-f1d8-403e8fe75d77@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).