qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.11] tests-aio-multithread: fix /aio/multi/schedule race condition
Date: Tue, 7 Nov 2017 12:29:18 +0100	[thread overview]
Message-ID: <1164825c-8f4a-ec21-0a29-ae0ff42bdb1d@redhat.com> (raw)
In-Reply-To: <20171106190233.1175-1-stefanha@redhat.com>

On 06/11/2017 20:02, Stefan Hajnoczi wrote:
> test_multi_co_schedule_entry() set to_schedule[id] in the final loop
> iteration before terminating the coroutine.  There is a race condition
> where the main thread attempts to enter the terminating or terminated
> coroutine when signalling coroutines to stop:
> 
>   atomic_mb_set(&now_stopping, true);
>   for (i = 0; i < NUM_CONTEXTS; i++) {
>       ctx_run(i, finish_cb, NULL);  <--- enters dead coroutine!
>       to_schedule[i] = NULL;
>   }
> 
> Make sure only to set to_schedule[id] if this coroutine really needs to
> be scheduled!
> 
> Reported-by: "R.Nageswara Sastry" <nasastry@in.ibm.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> This patch is appropriate for the QEMU 2.11 release to eliminate
> spurious test failures.
> 
>  tests/test-aio-multithread.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/test-aio-multithread.c b/tests/test-aio-multithread.c
> index 549d784915..d396185972 100644
> --- a/tests/test-aio-multithread.c
> +++ b/tests/test-aio-multithread.c
> @@ -144,17 +144,16 @@ static void finish_cb(void *opaque)
>  static coroutine_fn void test_multi_co_schedule_entry(void *opaque)
>  {
>      g_assert(to_schedule[id] == NULL);
> -    atomic_mb_set(&to_schedule[id], qemu_coroutine_self());
>  
>      while (!atomic_mb_read(&now_stopping)) {
>          int n;
>  
>          n = g_test_rand_int_range(0, NUM_CONTEXTS);
>          schedule_next(n);
> +
> +        atomic_mb_set(&to_schedule[id], qemu_coroutine_self());
>          qemu_coroutine_yield();
> -
>          g_assert(to_schedule[id] == NULL);
> -        atomic_mb_set(&to_schedule[id], qemu_coroutine_self());
>      }
>  }
>  
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

  reply	other threads:[~2017-11-07 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 19:02 [Qemu-devel] [PATCH for-2.11] tests-aio-multithread: fix /aio/multi/schedule race condition Stefan Hajnoczi
2017-11-07 11:29 ` Paolo Bonzini [this message]
2017-11-07 15:41 ` 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=1164825c-8f4a-ec21-0a29-ae0ff42bdb1d@redhat.com \
    --to=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).