From: Sean Christopherson <seanjc@google.com>
To: Lei Yang <leiyang@redhat.com>
Cc: Keith Busch <kbusch@meta.com>,
pbonzini@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux.dev, x86@kernel.org,
netdev@vger.kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 0/2]
Date: Fri, 28 Feb 2025 06:32:47 -0800 [thread overview]
Message-ID: <Z8HJD3m6YyCPrFMR@google.com> (raw)
In-Reply-To: <Z8HE-Ou-_9dTlGqf@google.com>
On Fri, Feb 28, 2025, Sean Christopherson wrote:
> On Fri, Feb 28, 2025, Lei Yang wrote:
> > Hi Keith
> >
> > V3 introduced a new bug, the following error messages from qemu output
> > after applying this patch to boot up a guest.
>
> Doh, my bug. Not yet tested, but this should fix things. Assuming it does, I'll
> post a v3 so I can add my SoB.
v4
Confirmed that it worked, but deleting the pre-mutex check for ONCE_COMPLETED.
Will post v4 later today.
> diff --git a/include/linux/call_once.h b/include/linux/call_once.h
> index ddcfd91493ea..b053f4701c94 100644
> --- a/include/linux/call_once.h
> +++ b/include/linux/call_once.h
> @@ -35,10 +35,12 @@ static inline int call_once(struct once *once, int (*cb)(struct once *))
> return 0;
>
> guard(mutex)(&once->lock);
> - WARN_ON(atomic_read(&once->state) == ONCE_RUNNING);
> - if (atomic_read(&once->state) != ONCE_NOT_STARTED)
> + if (WARN_ON(atomic_read(&once->state) == ONCE_RUNNING))
> return -EINVAL;
>
> + if (atomic_read(&once->state) == ONCE_COMPLETED)
> + return 0;
> +
> atomic_set(&once->state, ONCE_RUNNING);
> r = cb(once);
> if (r)
next prev parent reply other threads:[~2025-02-28 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 23:06 [PATCHv3 0/2] Keith Busch
2025-02-27 23:06 ` [PATCHv3 1/2] vhost: return task creation error instead of NULL Keith Busch
2025-02-28 18:34 ` Mike Christie
2025-02-27 23:06 ` [PATCHv3 2/2] kvm: retry nx_huge_page_recovery_thread creation Keith Busch
2025-03-04 15:59 ` Simon Horman
2025-03-04 16:07 ` Keith Busch
2025-05-01 15:12 ` Frederick Lawler
2025-02-28 8:07 ` [PATCHv3 0/2] Lei Yang
2025-02-28 14:15 ` Sean Christopherson
2025-02-28 14:32 ` Sean Christopherson [this message]
2025-02-28 14:58 ` Keith Busch
2025-02-28 15:29 ` Sean Christopherson
2025-02-28 15:36 ` Keith Busch
2025-02-28 16:43 ` Paolo Bonzini
2025-02-28 17:03 ` Sean Christopherson
2025-07-08 22:17 ` Keith Busch
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=Z8HJD3m6YyCPrFMR@google.com \
--to=seanjc@google.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=kvm@vger.kernel.org \
--cc=leiyang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=x86@kernel.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).