From: David Edmondson <david.edmondson@oracle.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Stefan Weil <sw@weilnetz.de>,
Max Reitz <mreitz@redhat.com>,
David Edmondson <david.edmondson@oracle.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH v2 4/6] test-coroutine: Add rwlock downgrade test
Date: Tue, 9 Mar 2021 14:40:13 +0000 [thread overview]
Message-ID: <20210309144015.557477-5-david.edmondson@oracle.com> (raw)
In-Reply-To: <20210309144015.557477-1-david.edmondson@oracle.com>
Test that downgrading an rwlock does not result in a failure to
schedule coroutines queued on the rwlock.
The diagram associated with test_co_rwlock_downgrade() describes the
intended behaviour, but what is observed currently corresponds to:
| c1 | c2 | c3 | c4 |
|--------+------------+------------+----------|
| rdlock | | | |
| yield | | | |
| | wrlock | | |
| | <queued> | | |
| | | rdlock | |
| | | <queued> | |
| | | | wrlock |
| | | | <queued> |
| unlock | | | |
| yield | | | |
| | <dequeued> | | |
| | downgrade | | |
| | ... | | |
| | unlock | | |
| | | <dequeued> | |
| | | <queued> | |
In the test, this results in a failure...
ERROR:../tests/test-coroutine.c:369:test_co_rwlock_downgrade: assertion failed: (c3_done)
Bail out! ERROR:../tests/test-coroutine.c:369:test_co_rwlock_downgrade: assertion failed: (c3_done)
...as a result of the c3 coroutine failing to run to completion.
Signed-off-by: David Edmondson <david.edmondson@oracle.com>
---
tests/test-coroutine.c | 112 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 112 insertions(+)
diff --git a/tests/test-coroutine.c b/tests/test-coroutine.c
index e946d93a65..62b0092721 100644
--- a/tests/test-coroutine.c
+++ b/tests/test-coroutine.c
@@ -264,6 +264,117 @@ static void test_co_mutex_lockable(void)
g_assert(QEMU_MAKE_LOCKABLE(null_pointer) == NULL);
}
+static bool c1_done;
+static bool c2_done;
+static bool c3_done;
+static bool c4_done;
+
+static void coroutine_fn rwlock_c1(void *opaque)
+{
+ CoRwlock *l = opaque;
+
+ qemu_co_rwlock_rdlock(l);
+ qemu_coroutine_yield();
+
+ qemu_co_rwlock_unlock(l);
+ qemu_coroutine_yield();
+
+ c1_done = true;
+}
+
+static void coroutine_fn rwlock_c2(void *opaque)
+{
+ CoRwlock *l = opaque;
+
+ qemu_co_rwlock_wrlock(l);
+
+ qemu_co_rwlock_downgrade(l);
+ qemu_co_rwlock_unlock(l);
+ c2_done = true;
+}
+
+static void coroutine_fn rwlock_c3(void *opaque)
+{
+ CoRwlock *l = opaque;
+
+ qemu_co_rwlock_rdlock(l);
+
+ qemu_co_rwlock_unlock(l);
+ c3_done = true;
+}
+
+static void coroutine_fn rwlock_c4(void *opaque)
+{
+ CoRwlock *l = opaque;
+
+ qemu_co_rwlock_wrlock(l);
+
+ qemu_co_rwlock_unlock(l);
+ c4_done = true;
+}
+
+/*
+ * Check that downgrading a reader-writer lock does not cause a hang.
+ *
+ * Four coroutines are used to produce a situation where there are
+ * both reader and writer hopefuls waiting to acquire an rwlock that
+ * is held by a reader.
+ *
+ * The correct sequence of operations we aim to provoke can be
+ * represented as:
+ *
+ * | c1 | c2 | c3 | c4 |
+ * |--------+------------+------------+------------|
+ * | rdlock | | | |
+ * | yield | | | |
+ * | | wrlock | | |
+ * | | <queued> | | |
+ * | | | rdlock | |
+ * | | | <queued> | |
+ * | | | | wrlock |
+ * | | | | <queued> |
+ * | unlock | | | |
+ * | yield | | | |
+ * | | <dequeued> | | |
+ * | | downgrade | | |
+ * | | ... | | |
+ * | | unlock | | |
+ * | | | | <dequeued> |
+ * | | | | unlock |
+ * | | | <dequeued> | |
+ * | | | unlock | |
+ *
+ * Significantly, when c2 unlocks the downgraded lock, it should be c4
+ * that is run rather than c3.
+ */
+static void test_co_rwlock_downgrade(void)
+{
+ CoRwlock l;
+ Coroutine *c1, *c2, *c3, *c4;
+
+ qemu_co_rwlock_init(&l);
+
+ c1 = qemu_coroutine_create(rwlock_c1, &l);
+ c2 = qemu_coroutine_create(rwlock_c2, &l);
+ c3 = qemu_coroutine_create(rwlock_c3, &l);
+ c4 = qemu_coroutine_create(rwlock_c4, &l);
+
+ qemu_coroutine_enter(c1);
+ qemu_coroutine_enter(c2);
+ qemu_coroutine_enter(c3);
+ qemu_coroutine_enter(c4);
+
+ qemu_coroutine_enter(c1);
+
+ g_assert(c2_done);
+ g_assert(c3_done);
+ g_assert(c4_done);
+
+ qemu_coroutine_enter(c1);
+
+ g_assert(c1_done);
+}
+
/*
* Check that creation, enter, and return work
*/
@@ -501,6 +612,7 @@ int main(int argc, char **argv)
g_test_add_func("/basic/order", test_order);
g_test_add_func("/locking/co-mutex", test_co_mutex);
g_test_add_func("/locking/co-mutex/lockable", test_co_mutex_lockable);
+ g_test_add_func("/locking/co-rwlock/downgrade", test_co_rwlock_downgrade);
if (g_test_perf()) {
g_test_add_func("/perf/lifecycle", perf_lifecycle);
g_test_add_func("/perf/nesting", perf_nesting);
--
2.30.1
next prev parent reply other threads:[~2021-03-09 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:40 [PATCH v2 0/6] coroutine rwlock downgrade fix, minor VDI changes David Edmondson
2021-03-09 14:40 ` [PATCH v2 1/6] block/vdi: When writing new bmap entry fails, don't leak the buffer David Edmondson
2021-03-09 14:40 ` [PATCH v2 2/6] block/vdi: Don't assume that blocks are larger than VdiHeader David Edmondson
2021-03-09 14:40 ` [PATCH v2 3/6] coroutine/mutex: Store the coroutine in the CoWaitRecord only once David Edmondson
2021-03-09 14:40 ` David Edmondson [this message]
2021-03-09 14:40 ` [PATCH v2 5/6] coroutine/rwlock: Wake writers in preference to readers David Edmondson
2021-03-09 14:40 ` [PATCH v2 6/6] coroutine/rwlock: Avoid thundering herd when unlocking David Edmondson
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=20210309144015.557477-5-david.edmondson@oracle.com \
--to=david.edmondson@oracle.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).