Bug 1195487

Summary: Windows guest performing out-of-bounds accesses on virtio device
Product: Red Hat Enterprise Linux 7 Reporter: Vadim Rozenfeld <vrozenfe>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: adevolder, areis, dgibson, jherrman, juzhang, knoel, lijin, mdeng, michen, mkalinin, rbalakri, rpacheco, virt-bugs, virt-maint, vrozenfe
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, Windows guests in some cases issued out-of-bounds read and write requests to a virtio device, which caused the guest to become unresponsive. Now, the Windows virtio-blk device drive performs logical block addressing (LBA) sanity checks before submitting requests to QEMU, and does not submit requests that are out-of-bounds. As a result, the described problem no longer occurs.
Story Points: ---
Clone Of: 1067225 Environment:
Last Closed: 2015-11-24 08:49:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1067225    
Bug Blocks: 1212392    

Comment 2 Vadim Rozenfeld 2015-04-23 02:37:28 UTC
Moving it back to assigned due to Bug 1212392

Comment 3 Vadim Rozenfeld 2015-05-24 08:29:51 UTC
please check with the latest build, available at http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/104/win/virtio-win-prewhql-0.1.zip

Comment 4 lijin 2015-05-28 02:44:32 UTC
Mike,please verify the bug with build104

Comment 8 lijin 2015-07-31 06:29:34 UTC
change status to verified according to comment#5 and bug1212392 is verified with build104

Comment 10 errata-xmlrpc 2015-11-24 08:49:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.