From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Pavel Butsykin <pbutsykin@virtuozzo.com>,
Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for 2.6 1/1] nbd: fix assert() on qemu-nbd stop
Date: Thu, 14 Apr 2016 16:40:31 +0300 [thread overview]
Message-ID: <570F9DCF.1070502@openvz.org> (raw)
In-Reply-To: <570F99C5.3050801@redhat.com>
On 04/14/2016 04:23 PM, Paolo Bonzini wrote:
>
> On 14/04/2016 12:20, Denis V. Lunev wrote:
>> From: Pavel Butsykin <pbutsykin@virtuozzo.com>
>>
>> From time to time qemu-nbd is crashing on the following assert:
>> assert(state == TERMINATING);
>> nbd_export_closed
>> nbd_export_put
>> main
>> and the state at the moment of the crash is evaluated to TERMINATE.
>>
>> During shutdown process of the client the nbd_client_thread thread sends
>> SIGTERM signal and the main thread calls the nbd_client_closed callback.
>> If the SIGTERM callback will be executed after change the state to
>> TERMINATING, then the state will once again be TERMINATE.
>>
>> To solve the issue, we must change the state to TERMINATE only if the state
>> is RUNNING. In the other case we are shutting down already.
>>
>> Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> qemu-nbd.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/qemu-nbd.c b/qemu-nbd.c
>> index ca4a724..956013f 100644
>> --- a/qemu-nbd.c
>> +++ b/qemu-nbd.c
>> @@ -213,7 +213,7 @@ static int find_partition(BlockBackend *blk, int partition,
>>
>> static void termsig_handler(int signum)
>> {
>> - state = TERMINATE;
>> + atomic_cmpxchg(&state, RUNNING, TERMINATE);
> Just a simple "if" is enough (the rest of the file is not using any of
> atomic{mb_,}{read,set}.
>
> I'm not able to send further pull requests for 2.6, can the block
> maintainers help?
>
> Paolo
unfortunately, if () would be not enough. The race is with different
thread which can run on the another CPU. Thus this OP should be
atomic or some locking is required.
Den
P.S. Added more block guys...
next prev parent reply other threads:[~2016-04-14 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 10:20 [Qemu-devel] [PATCH for 2.6 1/1] nbd: fix assert() on qemu-nbd stop Denis V. Lunev
2016-04-14 13:23 ` Paolo Bonzini
2016-04-14 13:40 ` Denis V. Lunev [this message]
2016-04-14 14:16 ` Paolo Bonzini
2016-04-14 21:41 ` Max Reitz
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=570F9DCF.1070502@openvz.org \
--to=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pbutsykin@virtuozzo.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).