From: w00214312 <wu.wubin@huawei.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, famz@redhat.com,
Bin Wu <wu.wubin@huawei.com>,
stefanha@redhat.com
Subject: [Qemu-devel] [PATCH] qemu-coroutine-lock: fix co_queue multi-adding bug
Date: Sat, 7 Feb 2015 17:51:48 +0800 [thread overview]
Message-ID: <1423302708-7900-2-git-send-email-wu.wubin@huawei.com> (raw)
In-Reply-To: <1423302708-7900-1-git-send-email-wu.wubin@huawei.com>
From: Bin Wu <wu.wubin@huawei.com>
When a coroutine holds a lock, other coroutines who want to get
the lock must wait on a co_queue by adding themselves to the
CoQueue. However, if a waiting coroutine is woken up with the
lock still be holding by other coroutine, this waiting coroutine
will add itself to the co_queue again. Latter, when the lock
is released, a coroutine re-enter will occur.
We need to determine whether a coroutine is alread in the co_queue
before adding it to the waiting queue.
Signed-off-by: Bin Wu <wu.wubin@huawei.com>
---
include/block/coroutine_int.h | 1 +
qemu-coroutine-lock.c | 6 +++++-
qemu-coroutine.c | 1 +
3 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/include/block/coroutine_int.h b/include/block/coroutine_int.h
index f133d65..c524990 100644
--- a/include/block/coroutine_int.h
+++ b/include/block/coroutine_int.h
@@ -42,6 +42,7 @@ struct Coroutine {
/* Coroutines that should be woken up when we yield or terminate */
QTAILQ_HEAD(, Coroutine) co_queue_wakeup;
QTAILQ_ENTRY(Coroutine) co_queue_next;
+ bool in_co_queue;
};
Coroutine *qemu_coroutine_new(void);
diff --git a/qemu-coroutine-lock.c b/qemu-coroutine-lock.c
index e4860ae..d256f53 100644
--- a/qemu-coroutine-lock.c
+++ b/qemu-coroutine-lock.c
@@ -36,7 +36,10 @@ void qemu_co_queue_init(CoQueue *queue)
void coroutine_fn qemu_co_queue_wait(CoQueue *queue)
{
Coroutine *self = qemu_coroutine_self();
- QTAILQ_INSERT_TAIL(&queue->entries, self, co_queue_next);
+ if (!self->in_co_queue) {
+ QTAILQ_INSERT_TAIL(&queue->entries, self, co_queue_next);
+ self->in_co_queue = true;
+ }
qemu_coroutine_yield();
assert(qemu_in_coroutine());
}
@@ -71,6 +74,7 @@ static bool qemu_co_queue_do_restart(CoQueue *queue, bool single)
while ((next = QTAILQ_FIRST(&queue->entries)) != NULL) {
QTAILQ_REMOVE(&queue->entries, next, co_queue_next);
+ next->in_co_queue = false;
QTAILQ_INSERT_TAIL(&self->co_queue_wakeup, next, co_queue_next);
trace_qemu_co_queue_next(next);
if (single) {
diff --git a/qemu-coroutine.c b/qemu-coroutine.c
index 525247b..a103721 100644
--- a/qemu-coroutine.c
+++ b/qemu-coroutine.c
@@ -75,6 +75,7 @@ Coroutine *qemu_coroutine_create(CoroutineEntry *entry)
}
co->entry = entry;
+ co->in_co_queue = false;
QTAILQ_INIT(&co->co_queue_wakeup);
return co;
}
--
1.7.12.4
next prev parent reply other threads:[~2015-02-07 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 9:51 [Qemu-devel] [PATCH] fix the co_queue multi-adding bug w00214312
2015-02-07 9:51 ` w00214312 [this message]
2015-02-09 8:12 ` [Qemu-devel] [PATCH] qemu-coroutine-lock: fix " Fam Zheng
2015-02-09 9:36 ` Bin Wu
2015-02-09 9:37 ` Paolo Bonzini
2015-02-09 10:12 ` Kevin Wolf
2015-02-10 1:08 ` Bin Wu
2015-02-09 9:23 ` [Qemu-devel] [PATCH] fix the " Paolo Bonzini
2015-02-09 9:47 ` Bin Wu
2015-02-10 6:34 ` Bin Wu
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=1423302708-7900-2-git-send-email-wu.wubin@huawei.com \
--to=wu.wubin@huawei.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).