From: Maxim Levitsky <mlevitsk@redhat.com>
To: Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] event_notifier: Set ->initialized earlier in event_notifier_init()
Date: Wed, 17 Feb 2021 16:59:22 +0200 [thread overview]
Message-ID: <d78503568990dc4ba59cf5b15dce5f95831508eb.camel@redhat.com> (raw)
In-Reply-To: <20210216120247.1293569-1-groug@kaod.org>
On Tue, 2021-02-16 at 13:02 +0100, Greg Kurz wrote:
> Otherwise the call to event_notifier_set() is a nop, which causes
> the SLOF firmware on POWER to hang when booting from a virtio-scsi
> device:
>
> virtio_scsi_dataplane_start()
> virtio_scsi_vring_init()
> virtio_bus_set_host_notifier() <- assign == true
> event_notifier_init() <- active == 1
> event_notifier_set() <- fails right away if !e->initialized
>
> Fixes: e34e47eb28c0 ("event_notifier: handle initialization failure better")
> Cc: mlevitsk@redhat.com
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> util/event_notifier-posix.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/event_notifier-posix.c b/util/event_notifier-posix.c
> index 5b2110e86198..8307013c5df0 100644
> --- a/util/event_notifier-posix.c
> +++ b/util/event_notifier-posix.c
> @@ -66,10 +66,10 @@ int event_notifier_init(EventNotifier *e, int active)
> e->rfd = fds[0];
> e->wfd = fds[1];
> }
> + e->initialized = true;
> if (active) {
> event_notifier_set(e);
> }
> - e->initialized = true;
> return 0;
>
> fail:
Sorry about that!
Best regards,
Maxim levitsky
prev parent reply other threads:[~2021-02-17 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 12:02 [PATCH] event_notifier: Set ->initialized earlier in event_notifier_init() Greg Kurz
2021-02-16 16:12 ` Paolo Bonzini
2021-02-17 14:59 ` Maxim Levitsky [this message]
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=d78503568990dc4ba59cf5b15dce5f95831508eb.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=groug@kaod.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).