From: Kevin Wolf <kwolf@redhat.com>
To: Feiran Zheng <famcool@gmail.com>
Cc: anthony.perard@citrix.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH]hw/xen_disk: aio_inflight not released in handling ioreq when nr_segments==0
Date: Wed, 09 Mar 2011 16:54:41 +0100 [thread overview]
Message-ID: <4D77A2C1.8030802@redhat.com> (raw)
In-Reply-To: <AANLkTi=AQm8-387iru=Fg++R+Fr0bGzJP0S3Oa28pWNt@mail.gmail.com>
Am 09.03.2011 14:19, schrieb Feiran Zheng:
> In hw/xen_disk.c, async writing ioreq is leaked when
> ioreq->req.nr_segments==0, because `aio_inflight` flag is not released
> properly (skipped by misplaced "break").
>
> Signed-off-by: Feiran Zheng <famcool@gmail.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2011-03-09 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:19 [Qemu-devel] [PATCH]hw/xen_disk: aio_inflight not released in handling ioreq when nr_segments==0 Feiran Zheng
2011-03-09 14:42 ` [Qemu-devel] " Stefano Stabellini
2011-03-09 14:42 ` Stefano Stabellini
2011-03-09 15:01 ` [Qemu-devel] " Stefan Hajnoczi
2011-03-09 15:01 ` Stefan Hajnoczi
2011-03-09 15:54 ` 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=4D77A2C1.8030802@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=famcool@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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.