[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DS0PR11MB6373F567D22270CA3CE86696DC499@DS0PR11MB6373.namprd11.prod.outlook.com>
Date: Thu, 1 Jun 2023 13:30:29 +0000
From: "Wang, Wei W" <wei.w.wang@...el.com>
To: "Christopherson,, Sean" <seanjc@...gle.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 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?
Thanks,
Wei
Powered by blists - more mailing lists