qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Feiran Zheng <famcool@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Kevin Wolf <kwolf@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: [PATCH]hw/xen_disk: ioreq not finished on error
Date: Tue, 29 Mar 2011 08:34:29 +0800	[thread overview]
Message-ID: <AANLkTi=-Pe9A3vLvmLMjw_aM1VddQ_uw0cEG08E4vdaz@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103281914230.5516@kaball-desktop>

Sorry for the confusing, I'll clean up it.

On Tue, Mar 29, 2011 at 2:16 AM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 28 Mar 2011, Feiran Zheng wrote:
>> On Mon, Mar 28, 2011 at 9:42 PM, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>> > On Sun, 27 Mar 2011, Feiran Zheng wrote:
>> >> Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio'
>> >> won't call 'ioreq_unmap' or 'ioreq_finish' on errors, leaving ioreq in
>> >> the blkdev->inflight list and a leak.
>> >>
>> >> Signed-off-by: Feiran Zheng <famcool@gmail.com>
>> >> ---
>> >>  hw/xen_disk.c |   22 +++++++++++++++++-----
>> >>  1 files changed, 17 insertions(+), 5 deletions(-)
>> >>
>> >> diff --git a/hw/xen_disk.c b/hw/xen_disk.c
>> >> index 445bf03..7940fab 100644
>> >> --- a/hw/xen_disk.c
>> >> +++ b/hw/xen_disk.c
>> >> @@ -309,8 +309,10 @@ static int ioreq_runio_qemu_sync(struct ioreq *ioreq)
>> >>      int i, rc, len = 0;
>> >>      off_t pos;
>> >>
>> >> -    if (ioreq->req.nr_segments && ioreq_map(ioreq) == -1)
>> >> -     goto err;
>> >> +    if (ioreq->req.nr_segments) {
>> >> +     if (ioreq_map(ioreq) == -1)
>> >> +         goto err_no_map;
>> >> +    }
>> >>      if (ioreq->presync)
>> >>       bdrv_flush(blkdev->bs);
>> >>
>> >
>> > this change is just to make the code clearer and easier to read, right?
>>
>> I think so.
>>
>> >
>> >
>> >> @@ -364,6 +366,9 @@ static int ioreq_runio_qemu_sync(struct ioreq *ioreq)
>> >>      return 0;
>> >>
>> >>  err:
>> >> +    ioreq_unmap(ioreq);
>> >> +err_no_map:
>> >> +    ioreq_finish(ioreq);
>> >>      ioreq->status = BLKIF_RSP_ERROR;
>> >>      return -1;
>> >>  }
>> >> @@ -392,8 +397,10 @@ static int ioreq_runio_qemu_aio(struct ioreq *ioreq)
>> >>  {
>> >>      struct XenBlkDev *blkdev = ioreq->blkdev;
>> >>
>> >> -    if (ioreq->req.nr_segments && ioreq_map(ioreq) == -1)
>> >> -     goto err;
>> >> +    if (ioreq->req.nr_segments) {
>> >> +     if (ioreq_map(ioreq) == -1)
>> >> +         goto err_no_map;
>> >> +    }
>> >>
>> >>      ioreq->aio_inflight++;
>> >>      if (ioreq->presync)
>> >> @@ -425,9 +432,14 @@ static int ioreq_runio_qemu_aio(struct ioreq *ioreq)
>> >>      qemu_aio_complete(ioreq, 0);
>> >>
>> >>      return 0;
>> >> +
>> >> +err_no_map:
>> >> +    ioreq_finish(ioreq);
>> >> +    ioreq->status = BLKIF_RSP_ERROR;
>> >> +    return -1;
>> >>
>> >
>> > why aren't you calling ioreq_unmap before ioreq_finish, like in the
>> > previous case?
>> >
>> >
>> >
>> It seems not a must but if call qemu_aio_complete, the error info can
>> be printed, I thought it may be helpful.
>
> I am not sure I understand what you mean here because in case of error
> we don't call qemu_aio_complete at all in the err_no_map code path.



-- 
Best regards!
Fam Zheng

  reply	other threads:[~2011-03-29  0:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 10:25 [Qemu-devel] [PATCH]hw/xen_disk: ioreq not finished on error Feiran Zheng
2011-03-28 13:42 ` [Qemu-devel] " Stefano Stabellini
2011-03-28 14:02   ` Feiran Zheng
2011-03-28 18:16     ` Stefano Stabellini
2011-03-29  0:34       ` Feiran Zheng [this message]
2011-03-29  1:00         ` [Qemu-devel] [PATCH V2] hw/xen_disk: " Feiran Zheng
2011-03-29 10:48           ` [Qemu-devel] " Stefano Stabellini
2011-03-29 11:50             ` Kevin Wolf

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='AANLkTi=-Pe9A3vLvmLMjw_aM1VddQ_uw0cEG08E4vdaz@mail.gmail.com' \
    --to=famcool@gmail.com \
    --cc=anthony.perard@citrix.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@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 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).