From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/vdi: Fix locking for parallel requests
Date: Fri, 27 Feb 2015 12:43:13 +0100 [thread overview]
Message-ID: <20150227114313.GF3174@noname.str.redhat.com> (raw)
In-Reply-To: <20150227112559.GB20354@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Am 27.02.2015 um 12:25 hat Stefan Hajnoczi geschrieben:
> On Tue, Feb 17, 2015 at 04:33:39PM -0500, Max Reitz wrote:
> > Concurrently modifying the bmap is not a good idea; this patch adds a
> > lock for it. See https://bugs.launchpad.net/qemu/+bug/1422307 for what
> > can go wrong without.
> >
> > Signed-off-by: Max Reitz <mreitz@redhat.com>
> > ---
> > block/vdi.c | 23 ++++++++++++++++++++---
> > 1 file changed, 20 insertions(+), 3 deletions(-)
>
> Max: Ping?
>
> Would be nice to merge a new revision with Paolo's comment addressed.
> Let's get it in for hard freeze (March 3rd) so that it gets testing
> during the release candidate phase.
And we still don't know _why_ this fixes anything.
If we're locking just because that's the obvious thing to try and it
appears to fix something, I would be much more comfortable with one
lock at the very start of the function, and one unlock at its very end,
plus a TODO comment that someone should figure out why it's needed.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2015-02-27 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 21:33 [Qemu-devel] [PATCH] block/vdi: Fix locking for parallel requests Max Reitz
2015-02-17 21:49 ` Paolo Bonzini
2015-02-17 21:49 ` Max Reitz
2015-02-18 7:52 ` Paolo Bonzini
2015-02-18 15:10 ` Max Reitz
2015-02-18 12:39 ` Kevin Wolf
2015-02-18 15:09 ` Max Reitz
2015-02-27 11:25 ` Stefan Hajnoczi
2015-02-27 11:43 ` Kevin Wolf [this message]
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=20150227114313.GF3174@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).