From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
syzbot+e87846c48bf72bc85311@syzkaller.appspotmail.com
Subject: Re: [PATCH] KVM: x86: fix shift out of bounds reported by UBSAN
Date: Tue, 22 Dec 2020 10:13:28 -0800 [thread overview]
Message-ID: <X+I3SFzLGhEZIzEa@google.com> (raw)
In-Reply-To: <20201222102132.1920018-1-pbonzini@redhat.com>
On Tue, Dec 22, 2020, Paolo Bonzini wrote:
> Since we know that e >= s, we can reassociate the left shift,
> changing the shifted number from 1 to 2 in exchange for
> decreasing the right hand side by 1.
I assume the edge case is that this ends up as `(1ULL << 64) - 1` and overflows
SHL's max shift count of 63 when s=0 and e=63? If so, that should be called
out. If it's something else entirely, then an explanation is definitely in
order.
> Reported-by: syzbot+e87846c48bf72bc85311@syzkaller.appspotmail.com
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/kvm/mmu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h
> index 9c4a9c8e43d9..581925e476d6 100644
> --- a/arch/x86/kvm/mmu.h
> +++ b/arch/x86/kvm/mmu.h
> @@ -49,7 +49,7 @@ static inline u64 rsvd_bits(int s, int e)
> if (e < s)
> return 0;
Maybe add a commment? Again assuming my guess about the edge case is on point.
/*
* Use 2ULL to incorporate the necessary +1 in the shift; adding +1 in
* the shift count will overflow SHL's max shift of 63 if s=0 and e=63.
*/
> - return ((1ULL << (e - s + 1)) - 1) << s;
> + return ((2ULL << (e - s)) - 1) << s;
> }
>
> void kvm_mmu_set_mmio_spte_mask(u64 mmio_value, u64 access_mask);
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-12-22 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 10:21 [PATCH] KVM: x86: fix shift out of bounds reported by UBSAN Paolo Bonzini
2020-12-22 18:13 ` Sean Christopherson [this message]
2020-12-22 18:31 ` David Laight
2020-12-22 22:49 ` Paolo Bonzini
2020-12-23 16: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=X+I3SFzLGhEZIzEa@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzbot+e87846c48bf72bc85311@syzkaller.appspotmail.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 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.