qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tong Zhang <t.zhang2@samsung.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "ztong0001@gmail.com" <ztong0001@gmail.com>,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	Tong Zhang <t.zhang2@samsung.com>,
	"Francisco Londono" <f.londono@samsung.com>
Subject: [RESEND PATCH] hw/dma: fix crash caused by race condition
Date: Fri, 6 May 2022 16:31:05 +0000	[thread overview]
Message-ID: <20220506163059.2517-1-t.zhang2@samsung.com> (raw)
In-Reply-To: CGME20220506163106uscas1p20aa8ba0a290a9b50be54df6ec4f9cee0@uscas1p2.samsung.com

assert(dbs->acb) is meant to check the return value of io_func per
documented in commit 6bee44ea34 ("dma: the passed io_func does not
return NULL"). However, there is a chance that after calling
aio_context_release(dbs->ctx); the dma_blk_cb function is called before
the assertion and dbs->acb is set to NULL again at line 121. Thus when
we run assert at line 181 it will fail.

  softmmu/dma-helpers.c:181: dma_blk_cb: Assertion `dbs->acb' failed.

Reported-by: Francisco Londono <f.londono@samsung.com>
Signed-off-by: Tong Zhang <t.zhang2@samsung.com>
---
 softmmu/dma-helpers.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/softmmu/dma-helpers.c b/softmmu/dma-helpers.c
index 7820fec54c..cb81017928 100644
--- a/softmmu/dma-helpers.c
+++ b/softmmu/dma-helpers.c
@@ -177,8 +177,8 @@ static void dma_blk_cb(void *opaque, int ret)
     aio_context_acquire(dbs->ctx);
     dbs->acb = dbs->io_func(dbs->offset, &dbs->iov,
                             dma_blk_cb, dbs, dbs->io_func_opaque);
-    aio_context_release(dbs->ctx);
     assert(dbs->acb);
+    aio_context_release(dbs->ctx);
 }
 
 static void dma_aio_cancel(BlockAIOCB *acb)
-- 
2.25.1


       reply	other threads:[~2022-05-06 16:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220506163106uscas1p20aa8ba0a290a9b50be54df6ec4f9cee0@uscas1p2.samsung.com>
2022-05-06 16:31 ` Tong Zhang [this message]
2022-06-28 22:34   ` [RESEND PATCH] hw/dma: fix crash caused by race condition Laurent Vivier
2022-06-29  7:28   ` David Hildenbrand
2022-06-29  8:31     ` Tong Zhang
2022-06-29  9:52       ` David Hildenbrand
     [not found] <CGME20220427205118uscas1p25031437c0cdd4363c104be13033f366a@uscas1p2.samsung.com>
2022-04-27 20:51 ` Tong Zhang
2022-05-30 14:34   ` Philippe Mathieu-Daudé via
2022-05-30 16:19   ` David Hildenbrand
2022-06-01  0:20     ` Tong Zhang
2022-06-01  8:00       ` David Hildenbrand
2022-06-01 13:24         ` Stefan Hajnoczi
2022-06-01 13:29           ` David Hildenbrand
2022-06-01 13:55             ` Stefan Hajnoczi
2022-06-02  1:04               ` Tong Zhang
2022-06-02  5:29                 ` 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=20220506163059.2517-1-t.zhang2@samsung.com \
    --to=t.zhang2@samsung.com \
    --cc=david@redhat.com \
    --cc=f.londono@samsung.com \
    --cc=f4bug@amsat.org \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=ztong0001@gmail.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).