From: Wei Wang <wei.w.wang@intel.com>
To: pbonzini@redhat.com, seanjc@google.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Wei Wang <wei.w.wang@intel.com>
Subject: [PATCH v1] KVM: allow KVM_BUG/KVM_BUG_ON to handle 64-bit cond
Date: Wed, 1 Mar 2023 21:38:41 +0800 [thread overview]
Message-ID: <20230301133841.18007-1-wei.w.wang@intel.com> (raw)
Current KVM_BUG and KVM_BUG_ON assumes that 'cond' passed from callers is
32-bit as it casts 'cond' to the type of int. This will be wrong if 'cond'
provided by a caller is 64-bit, e.g. an error code of 0xc0000d0300000000
will be converted to 0, which is not expected. Improves the implementation
by using !!(cond) in KVM_BUG and KVM_BUG_ON. Compared to changing 'int' to
'int64_t', this has less LOCs.
Fixes: 0b8f11737cff ("KVM: Add infrastructure and macro to mark VM as bugged")
Signed-off-by: Wei Wang <wei.w.wang@intel.com>
---
include/linux/kvm_host.h | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index f06635b24bd0..d77ddf82c5c8 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -881,20 +881,16 @@ static inline void kvm_vm_bugged(struct kvm *kvm)
#define KVM_BUG(cond, kvm, fmt...) \
({ \
- int __ret = (cond); \
- \
- if (WARN_ONCE(__ret && !(kvm)->vm_bugged, fmt)) \
+ if (WARN_ONCE(!!cond && !(kvm)->vm_bugged, fmt)) \
kvm_vm_bugged(kvm); \
- unlikely(__ret); \
+ unlikely(!!cond); \
})
#define KVM_BUG_ON(cond, kvm) \
({ \
- int __ret = (cond); \
- \
- if (WARN_ON_ONCE(__ret && !(kvm)->vm_bugged)) \
+ if (WARN_ON_ONCE(!!(cond) && !(kvm)->vm_bugged)) \
kvm_vm_bugged(kvm); \
- unlikely(__ret); \
+ unlikely(!!(cond)); \
})
static inline void kvm_vcpu_srcu_read_lock(struct kvm_vcpu *vcpu)
--
2.27.0
next reply other threads:[~2023-03-01 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 13:38 Wei Wang [this message]
2023-03-01 18:30 ` [PATCH v1] KVM: allow KVM_BUG/KVM_BUG_ON to handle 64-bit cond Mingwei Zhang
2023-03-01 19:47 ` David Matlack
2023-03-02 2:00 ` Wang, Wei W
2023-03-02 4:54 ` Mingwei Zhang
2023-03-02 10:26 ` Wang, Wei W
2023-03-02 18:12 ` Mingwei Zhang
2023-03-03 1:49 ` Wang, Wei W
2023-03-03 5:53 ` Mingwei Zhang
2023-03-03 17:36 ` David Matlack
2023-03-04 4:25 ` Wang, Wei W
2023-03-06 20:34 ` Sean Christopherson
2023-03-02 1:17 ` Isaku Yamahata
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=20230301133841.18007-1-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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