All of lore.kernel.org
 help / color / mirror / Atom feed
From: mlevitsk@redhat.com
To: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org,  kvm@vger.kernel.org
Cc: Yuntao Liu <liuyuntao12@huawei.com>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH] KVM: x86: avoid underflow when scaling TSC frequency
Date: Wed, 09 Jul 2025 14:08:42 -0400	[thread overview]
Message-ID: <dfd970bb10235adfa2b2b545ea26bffba1ea3a66.camel@redhat.com> (raw)
In-Reply-To: <20250709175303.228675-1-pbonzini@redhat.com>

On Wed, 2025-07-09 at 13:53 -0400, Paolo Bonzini wrote:
> In function kvm_guest_time_update(), __scale_tsc() is used to calculate
> a TSC *frequency* rather than a TSC value.  With low-enough ratios,
> a TSC value that is less than 1 would underflow to 0 and to an infinite
> while loop in kvm_get_time_scale():
> 
>   kvm_guest_time_update(struct kvm_vcpu *v)
>     if (kvm_caps.has_tsc_control)
>       tgt_tsc_khz = kvm_scale_tsc(tgt_tsc_khz,
>                                   v->arch.l1_tsc_scaling_ratio);
>         __scale_tsc(u64 ratio, u64 tsc)
>           ratio=122380531, tsc=2299998, N=48
>           ratio*tsc >> N = 0.999... -> 0
> 
> Later in the function:
> 
>   Call Trace:
>    <TASK>
>    kvm_get_time_scale arch/x86/kvm/x86.c:2458 [inline]
>    kvm_guest_time_update+0x926/0xb00 arch/x86/kvm/x86.c:3268
>    vcpu_enter_guest.constprop.0+0x1e70/0x3cf0 arch/x86/kvm/x86.c:10678
>    vcpu_run+0x129/0x8d0 arch/x86/kvm/x86.c:11126
>    kvm_arch_vcpu_ioctl_run+0x37a/0x13d0 arch/x86/kvm/x86.c:11352
>    kvm_vcpu_ioctl+0x56b/0xe60 virt/kvm/kvm_main.c:4188
>    vfs_ioctl fs/ioctl.c:51 [inline]
>    __do_sys_ioctl fs/ioctl.c:871 [inline]
>    __se_sys_ioctl+0x12d/0x190 fs/ioctl.c:857
>    do_syscall_x64 arch/x86/entry/common.c:51 [inline]
>    do_syscall_64+0x59/0x110 arch/x86/entry/common.c:81
>    entry_SYSCALL_64_after_hwframe+0x78/0xe2
> 
> This can really happen only when fuzzing, since the TSC frequency
> would have to be nonsensically low.
> 
> Fixes: 35181e86df97 ("KVM: x86: Add a common TSC scaling function")
> Reported-by: Yuntao Liu <liuyuntao12@huawei.com>
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  arch/x86/kvm/x86.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index b58a74c1722d..de51dbd85a58 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -3258,9 +3258,11 @@ int kvm_guest_time_update(struct kvm_vcpu *v)
>  
>  	/* With all the info we got, fill in the values */
>  
> -	if (kvm_caps.has_tsc_control)
> +	if (kvm_caps.has_tsc_control) {
>  		tgt_tsc_khz = kvm_scale_tsc(tgt_tsc_khz,
>  					    v->arch.l1_tsc_scaling_ratio);
> +		tgt_tsc_khz = tgt_tsc_khz ? : 1;
> +	}
>  
>  	if (unlikely(vcpu->hw_tsc_khz != tgt_tsc_khz)) {
>  		kvm_get_time_scale(NSEC_PER_SEC, tgt_tsc_khz * 1000LL,

Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>

Best regards,
	Maxim Levitsky


      reply	other threads:[~2025-07-09 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 17:53 [PATCH] KVM: x86: avoid underflow when scaling TSC frequency Paolo Bonzini
2025-07-09 18:08 ` mlevitsk [this message]

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=dfd970bb10235adfa2b2b545ea26bffba1ea3a66.camel@redhat.com \
    --to=mlevitsk@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyuntao12@huawei.com \
    --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 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.