[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZHjDra1HbG65o4uH@google.com>
Date: Thu, 1 Jun 2023 09:20:54 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Wei W Wang <wei.w.wang@...el.com>
Cc: "dmatlack@...gle.com" <dmatlack@...gle.com>,
"mizhang@...gle.com" <mizhang@...gle.com>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] KVM: allow KVM_BUG/KVM_BUG_ON to handle 64-bit cond
On Thu, Jun 01, 2023, Wei W Wang wrote:
> On Thursday, March 9, 2023 7:26 AM, Sean Christopherson wrote:
> > On Tue, Mar 07, 2023, Wei Wang wrote:
> > > Current KVM_BUG and KVM_BUG_ON assume that 'cond' passed from
> > callers
> > > is 32-bit as it casts 'cond' to the type of int.
> >
> > You're very generous, I would have led with "Fix a badly done
> > copy+paste ..." ;-)
> >
> > > Fixes: 0b8f11737cff ("KVM: Add infrastructure and macro to mark VM as
> > > bugged")
> > > Signed-off-by: Wei Wang <wei.w.wang@...el.com>
> > > ---
> >
> > Reviewed-by: Sean Christopherson <seanjc@...gle.com>
>
> Kind ping on this patch.
> Seems it wasn't noticed for months. Just check if it would be good to be
> merged or not proper for any reason?
I'll grab it for 6.5.
Powered by blists - more mailing lists