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 1310511 - About patch "aio: strengthen memory barriers for bottom half scheduling"
Summary: About patch "aio: strengthen memory barriers for bottom half scheduling"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1356849 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 05:06 UTC by Yuki Shibuya
Modified: 2016-07-18 14:47 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 17:39:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Yuki Shibuya 2016-02-22 05:06:51 UTC 
Description of problem:

We recently faced the problem mentioned in below patch on other distribution.
And our problem was solved by this patch.

http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e8d3b1a25f284cdf9705b7cf0412281cc9ee3a36

Does this problem occur in RHEL 7 ?

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

$ rpm -qa | grep qemu
qemu-img-1.5.3-86.el7_1.5.x86_64
qemu-kvm-1.5.3-86.el7_1.5.x86_64
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.3.x86_64
qemu-kvm-tools-1.5.3-86.el7_1.5.x86_64
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
qemu-kvm-common-1.5.3-86.el7_1.5.x86_64

How reproducible:

Sorry, I have not tried. However, the reproduce procedure is explained in
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e8d3b1a25f284cdf9705b7cf0412281cc9ee3a36

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Paolo Bonzini 2016-02-26 12:58:39 UTC 
Hi, the bug was introduced upstream by commit c2e50e3d11a0bf4c973cc30478c1af0f2d5f8e81 (thread-pool: avoid per-thread-pool EventNotifier).  Until that commit, the code in async.c is safe because bottom halves are never used across threads.  Thus:

- the qemu-kvm package, as well as the qemu-kvm-rhev-1.5.3 package is immune from the bug.

- the qemu-kvm-rhev-2.1.2 package has the bug

- the qemu-kvm-rhev-2.3.0 package has the above patch and the fix, and thus is also immune from the bug

Please close the bug if you are only interested in the 1.5.3 versions, or request the rhel-7.1.z flag if you are interested in a fix for qemu-kvm-rhev-2.1.2.
Comment 3 Yuki Shibuya 2016-02-29 02:09:57 UTC 
I appreciate your kind support.

We know the bug does not occur in qemu-kvm 1.5.3 versions by your answer.
We plan to use 1.5.3 versions, therefore I want to close this bug report as NOTABUG. 
Sorry, I couldn't find how to close bug. Can you please teach me how to close bug ?
Comment 4 Paolo Bonzini 2016-03-07 17:39:10 UTC 
Closing.  You might not have permissions to close bugs; here I see a dropdown control labelled "Status:" below the comment box.
Comment 5 Yuki Shibuya 2016-03-08 00:33:50 UTC 
(In reply to Paolo Bonzini from comment #4)
> Closing.  You might not have permissions to close bugs; here I see a
> dropdown control labelled "Status:" below the comment box.

Thank you.

Just as you say, I didn't probably have permission. I couldn't change a dropdown control labelled "Status:" at last time.
Comment 6 Paolo Bonzini 2016-07-18 14:47:54 UTC 
*** Bug 1356849 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.