From: Sean Christopherson <seanjc@google.com>
To: Yosry Ahmed <yosry@kernel.org>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Teodorescu <fane@google.com>
Subject: Re: [PATCH 0/2] KVM: x86: Convert all runtime WARNs to ONCE
Date: Mon, 26 Oct 2026 10:35:58 -0700 [thread overview]
Message-ID: <at-Pfgjt__PJl55M@google.com> (raw)
In-Reply-To: <CAO9r8zPFEwUVYSTePWN-FurHLzGN6cY8bd-BOj3sjRmjj4xQbA@mail.gmail.com>
On Fri, Oct 23, 2026, Yosry Ahmed wrote:
> On Thu, Oct 22, 2026 at 2:55 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > Convert all bare WARN() and WARN_ON() runtime usage, i.e. WARNs that aren't
> > strictly scoped to module init/exit, or similar, to ONCE() variants for what
> > should be fairly obvious reasons at this point.
>
> Do you wanna CC stable?
Not really? Maybe? I worry that this will generate an absurd number of conflicts
and also have "misses" in older kernels, to the point where it oculd do more harm
than good.
I could be convinced this should be tagged for stable@, though honestly it might
be better to omit the automatic backport trigger and just rely on someone to
"manually" provide equivalent patches.
next prev parent reply other threads:[~2026-10-26 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:55 [PATCH 0/2] KVM: x86: Convert all runtime WARNs to ONCE Sean Christopherson
2026-10-22 21:55 ` [PATCH 1/2] KVM: x86: Convert WARN_ON(preemptible()) to lockdep assertion Sean Christopherson
2026-10-22 21:55 ` [PATCH 2/2] KVM: x86: Convert all runtime WARNs to ONCE variants Sean Christopherson
2026-10-22 22:02 ` sashiko-bot
2026-10-22 22:05 ` Sean Christopherson
2026-10-23 14:59 ` [PATCH 0/2] KVM: x86: Convert all runtime WARNs to ONCE Yosry Ahmed
2026-10-26 17:35 ` Sean Christopherson [this message]
2026-10-26 18:04 ` Yosry Ahmed
2026-10-26 18:38 ` Vitaly Kuznetsov
2026-10-26 18:59 ` Sean Christopherson
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=at-Pfgjt__PJl55M@google.com \
--to=seanjc@google.com \
--cc=fane@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=yosry@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.