mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org
Cc: y2038@lists.linaro.org,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	Andrey Smetanin <asmetanin@virtuozzo.com>,
	"Denis V. Lunev" <den@openvz.org>,
	Haozhong Zhang <haozhong.zhang@intel.com>,
	Feng Wu <feng.wu@intel.com>,
	Steve Rutherford <srutherford@google.com>,
	Andy Lutomirski <luto@kernel.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: x86: use getboottime64
Date: Thu, 23 Jun 2016 19:15:15 +0200	[thread overview]
Message-ID: <b54f1377-d7db-0b0c-7b27-e9a785491fc5@redhat.com> (raw)
In-Reply-To: <20160617154914.660326-1-arnd@arndb.de>



On 17/06/2016 17:48, Arnd Bergmann wrote:
> KVM reads the current boottime value as a struct timespec in order to
> calculate the guest wallclock time, resulting in an overflow in 2038
> on 32-bit systems.
> 
> The data then gets passed as an unsigned 32-bit number to the guest,
> and that in turn overflows in 2106.
> 
> We cannot do much about the second overflow, which affects both 32-bit
> and 64-bit hosts, but we can ensure that they both behave the same
> way and don't overflow until 2106, by using getboottime64() to read
> a timespec64 value.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  arch/x86/kvm/x86.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 53241618e3c9..f79c86510408 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1163,7 +1163,7 @@ static void kvm_write_wall_clock(struct kvm *kvm, gpa_t wall_clock)
>  	int version;
>  	int r;
>  	struct pvclock_wall_clock wc;
> -	struct timespec boot;
> +	struct timespec64 boot;
>  
>  	if (!wall_clock)
>  		return;
> @@ -1186,13 +1186,13 @@ static void kvm_write_wall_clock(struct kvm *kvm, gpa_t wall_clock)
>  	 * wall clock specified here.  guest system time equals host
>  	 * system time for us, thus we must fill in host boot time here.
>  	 */
> -	getboottime(&boot);
> +	getboottime64(&boot);
>  
>  	if (kvm->arch.kvmclock_offset) {
> -		struct timespec ts = ns_to_timespec(kvm->arch.kvmclock_offset);
> -		boot = timespec_sub(boot, ts);
> +		struct timespec64 ts = ns_to_timespec64(kvm->arch.kvmclock_offset);
> +		boot = timespec64_sub(boot, ts);
>  	}
> -	wc.sec = boot.tv_sec;
> +	wc.sec = (u32)boot.tv_sec; /* overflow in 2106 guest time */
>  	wc.nsec = boot.tv_nsec;
>  	wc.version = version;
>  
> 

Queued, thanks.

Paolo

      reply	other threads:[~2016-06-23 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17 15:48 Arnd Bergmann
2016-06-23 17:15 ` Paolo Bonzini [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=b54f1377-d7db-0b0c-7b27-e9a785491fc5@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arnd@arndb.de \
    --cc=asmetanin@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=feng.wu@intel.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=srutherford@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=y2038@lists.linaro.org \
    /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

all inboxes | Powered by JetHome®