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 1225188 - librbd: aio calls may block
Summary: librbd: aio calls may block
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ceph-common
Version: 7.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Boris Ranto
QA Contact: Warren
URL:
Whiteboard:
: 1225189 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-26 19:00 UTC by Josh Durgin
Modified: 2016-02-09 21:51 UTC (History)
6 users (show)

Fixed In Version: ceph-common-0.80.7-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1225171
Environment:
Last Closed: 2015-11-19 11:45:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 11056 0 None None None Never
Red Hat Product Errata RHBA-2015:2348 0 normal SHIPPED_LIVE ceph-common bug fix update 2015-11-19 10:29:45 UTC

Description Josh Durgin 2015-05-26 19:00:29 UTC
+++ This bug was initially created as a clone of Bug #1225171 +++

QEMU runs these from its threads, so blocking here causes the vcpu to lock up from the guest's perspective, resulting in messages in linux guests like

BUG: soft lockup - CPU#1 stuck for 520s!

One cause that has been observed is via Objecter-level throttling of requests:

With caching disabled, this blocks directly in aio_read/write().

With caching enabled, the cache does i/o while holding its lock, and if it is throttled in its flusher thread, for example, readx() and writex() will block waiting on the cache lock.

Comment 4 Boris Ranto 2015-06-17 18:15:56 UTC
Scratch build with the patches for the issue:

https://brewweb.devel.redhat.com/taskinfo?taskID=9379871

-> setting devel_ack+.

@Jason: This bz is for base rhel-7.2, the patches are not (can't be, yet) submitted to base rhel, moving back to ASSIGNED.

Comment 5 Boris Ranto 2015-06-17 18:17:03 UTC
*** Bug 1225189 has been marked as a duplicate of this bug. ***

Comment 7 Boris Ranto 2015-06-19 12:08:41 UTC
dist-git commits related to build ceph-common-0.80.7-3.el7:
http://pkgs.devel.redhat.com/cgit/rpms/ceph-common/commit/?h=rhel-7.2&id=4844e939f3bf9b945e3bd6713f475fcb0d12d329

Comment 10 errata-xmlrpc 2015-11-19 11:45:00 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.

https://rhn.redhat.com/errata/RHBA-2015-2348.html


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