qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: ChenLiang <chenliang88@huawei.com>
Cc: kwolf@redhat.com, arei.gonglei@huawei.com,
	weidong.huang@huawei.com, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ide: fix double free
Date: Wed, 02 Jul 2014 11:25:37 +0200	[thread overview]
Message-ID: <53B3D011.9000200@redhat.com> (raw)
In-Reply-To: <53B3CFB8.5000800@huawei.com>

Il 02/07/2014 11:24, ChenLiang ha scritto:
> On 2014/7/2 17:04, Paolo Bonzini wrote:
>
>> This is definitely a heavyweight solution, and in fact the bug should
>> not be there in the first place.  See dma_complete:
>>
>> static void dma_complete(DMAAIOCB *dbs, int ret)
>> {
>>     trace_dma_complete(dbs, ret, dbs->common.cb);
>>
>>     dma_bdrv_unmap(dbs);
>>     if (dbs->common.cb) {
>>         dbs->common.cb(dbs->common.opaque, ret);
>>     }
>>     qemu_iovec_destroy(&dbs->iov);
>>     if (dbs->bh) {
>>         qemu_bh_delete(dbs->bh);
>>         dbs->bh = NULL;
>>     }
>>     if (!dbs->in_cancel) {
>>         /* Requests may complete while dma_aio_cancel is in progress.  In
>>          * this case, the AIOCB should not be released because it is still
>>          * referenced by dma_aio_cancel.  */
>>         qemu_aio_release(dbs);
>>     }
>> }
>>
>> Perhaps something like this?
>>
>> diff --git a/dma-helpers.c b/dma-helpers.c
>> index 53cbe92..21b70d12 100644
>> --- a/dma-helpers.c
>> +++ b/dma-helpers.c
>> @@ -181,15 +181,15 @@ static void dma_aio_cancel(BlockDriverAIOCB *acb)
>>
>>      trace_dma_aio_cancel(dbs);
>>
>> +    dbs->in_cancel = true;
>>      if (dbs->acb) {
>>          BlockDriverAIOCB *acb = dbs->acb;
>>          dbs->acb = NULL;
>> -        dbs->in_cancel = true;
>>          bdrv_aio_cancel(acb);
>> -        dbs->in_cancel = false;
>>      }
>>      dbs->common.cb = NULL;
>>      dma_complete(dbs, 0);
>> +    qemu_aio_release(dbs);
>>  }
>>
>>  static const AIOCBInfo dma_aiocb_info = {
>>
>>
>> .
>>
>
> acked, thanks

Did you test this? :)  What is the testcase?

Paolo

  reply	other threads:[~2014-07-02  9:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  8:50 [Qemu-devel] [PATCH] ide: fix double free arei.gonglei
2014-07-02  9:04 ` Paolo Bonzini
2014-07-02  9:24   ` ChenLiang
2014-07-02  9:25     ` Paolo Bonzini [this message]
2014-07-02  9:46       ` Gonglei (Arei)
2014-07-02 10:16         ` Paolo Bonzini
2014-07-02 11:12           ` ChenLiang
2014-07-02 11:24             ` Paolo Bonzini
2014-07-02 11:33           ` ChenLiang
2014-07-02 11:40             ` Paolo Bonzini
2014-07-02 11:57               ` ChenLiang
2014-07-02 12:19                 ` Paolo Bonzini
2014-07-02 12:46                   ` 陈梁
2014-07-02 12:54                   ` 陈梁
2014-07-02 13:09                     ` Paolo Bonzini
2014-07-03  2:23                   ` ChenLiang
2014-07-03 10:41                     ` Paolo Bonzini
2014-07-07  8:12                       ` ChenLiang
2014-07-07 12:38                         ` Paolo Bonzini

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=53B3D011.9000200@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=chenliang88@huawei.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.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).