Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2035659

Summary: BSOD of fwcfg64 driver (driver verifier violation)
Product: Red Hat Enterprise Linux 9 Reporter: ybendito
Component: virtio-winAssignee: Viktor Prutyanov <vprutyan>
virtio-win sub component: virtio-win-prewhql QA Contact: Peixiu Hou <phou>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: coli, jinzhao, juzhang, mdean, qizhu, vprutyan, ybendito, yvugenfi
Version: 9.0Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:35:27 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:
Embargoed:

Description ybendito 2021-12-26 15:36:55 UTC
Description of problem:

BSOD happened during automated test of fwcfg64 driver
The reason is "driver verifier violation", attempt to allocate 0 bytes.


Version-Release number of selected component (if applicable):

214

How reproducible:

Once, not always

Steps to Reproduce:
Happened during acceptance testing on Win8.1

Actual results:

The driver successfully allocated 256K, calls KeCapturePersistentThreadState, does not check any result, then read required number of bytes to allocate from the header, got number 0 (the header indeed contains zeroed at 0x2070 and 0x2074) and tries to allocate 0 bytes.

Expected results:

Probably should fail the initialization or just fail to function but not try to allocate illegal size.

Dump file is available upon request

Additional info:

Comment 1 Yvugenfi@redhat.com 2021-12-28 12:50:36 UTC
Upstream fix: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/697

Comment 3 Peixiu Hou 2022-01-04 11:29:19 UTC
Hi Yuri,

I'm running the acceptance tests to reproduce this issue, but has not reproduced it now, since it's not 100%, do you have any other advise for reproduce/verify it more easier?

Thanks~
Peixiu

Comment 4 Peixiu Hou 2022-01-06 08:30:40 UTC
And I also want to know which job hit BSOD during acceptance testing on Win8.1? I tried to run the whole acceptance loop some times, but not hit BSOD occur.

Thanks~
Peixiu

Comment 9 Viktor Prutyanov 2022-02-23 19:41:56 UTC
As I remember after discussion with Yuri, it was caused by running fwcfg64 driver on 32-bit Windows, but at that date the driver did not yet have a 32-bit version.
So, to reproduce it fwcfg64 must be run on 32-bit Windows. 
The 32-bit version were introduced in upstream commit https://github.com/virtio-win/kvm-guest-drivers-windows/commit/f1ba15c6cc09a191807342e250a00fb0f3f40564 .

Comment 10 Peixiu Hou 2022-02-25 09:51:20 UTC
(In reply to Viktor Prutyanov from comment #9)
> As I remember after discussion with Yuri, it was caused by running fwcfg64
> driver on 32-bit Windows, but at that date the driver did not yet have a
> 32-bit version.
> So, to reproduce it fwcfg64 must be run on 32-bit Windows. 
> The 32-bit version were introduced in upstream commit
> https://github.com/virtio-win/kvm-guest-drivers-windows/commit/
> f1ba15c6cc09a191807342e250a00fb0f3f40564 .

Hi Viktor,

If possible, Could you help to create a downgrade test build with 32-bit support? 

And BTW, Bug 1983947 - [RFE] Add support for fwcfg64 driver - 32 bits used to track fwcfg 32 bits support, it has been remove to RHL9.1, but as I known, this fix has been included in build 216, will released with RHEL9.0, so If this fix is related to 32 bits system, Is it better merge both on the same target release?

Thanks a lot~
Peixiu

Comment 11 Peixiu Hou 2022-02-28 01:47:05 UTC
Not reproducible for now, moving this to VERIFIED since regression test passed on 64 bit Windows OSes. We will open new bz if detect issue on 32 bit fwcfg when it is released in future~

Thanks~

Comment 14 errata-xmlrpc 2022-05-17 15:35:27 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 (new packages: virtio-win), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2022:3890