Bug 557095 - kvm pvclock on i386 suffers from double registering
Summary: kvm pvclock on i386 suffers from double registering
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Glauber Costa
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 528898 561454
TreeView+ depends on / blocked
 
Reported: 2010-01-20 12:21 UTC by Glauber Costa
Modified: 2013-01-09 22:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 06:53:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0178 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.5 kernel security and bug fix update 2010-03-29 12:18:21 UTC

Description Glauber Costa 2010-01-20 12:21:09 UTC
By looking at the dmesg on a i386 kvm guest with pvclock enabled, I noticed that we're registering the boot clock after primary and secondary clock are already registered, as part of the cpu identification code.

This causes kvm to write data to a random memory area during guest's life.

Comment 1 Glauber Costa 2010-01-20 18:36:01 UTC
I just posted it, definitely for 5.6.

But maybe we should consider it for 5.5 post beta too. Fix is not hard and not invasive.

Comment 2 RHEL Program Management 2010-01-21 07:30:39 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 12 errata-xmlrpc 2010-03-30 06:53:29 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0178.html


Note You need to log in before you can comment on or make changes to this bug.