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.
Reproducible:
always
Version-Release number of selected component (if applicable):
RHEL6.0-20100523.0
blktrace-1.0.1-3.1.el6.x86_64
kernel-2.6.32-28.el6.x86_64
Steps to Reproduce:
# blktrace -d /dev/sda -w 30
=== sda ===
CPU 0: 17 events, 1 KiB data
CPU 1: 1 events, 1 KiB data
CPU 2: 84 events, 4 KiB data
CPU 3: 255 events, 12 KiB data
Total: 357 events (dropped 0), 17 KiB data
# ls -l *.blktrace.*
-rw-r--r--. 1 root root 818 May 24 08:13 sda.blktrace.0
-rw-r--r--. 1 root root 68 May 24 08:13 sda.blktrace.1
-rw-r--r--. 1 root root 4073 May 24 08:13 sda.blktrace.2
-rw-r--r--. 1 root root 12272 May 24 08:13 sda.blktrace.3
# rm -f sda.blktrace.0
# mkdir sda.blktrace.0
# blktrace -d /dev/sda -w 30
Open output file ./sda.blktrace.0 failed: 21/Is a directory
FAILED to start thread on CPU 0: 1/Operation not permitted
Actual results:
blktrace does not end after 30 seconds, it will be running until you kill it
Expected results:
blktrace terminates either immediately (because of the error message) or after 30 seconds (because of the run time option)
The bug:
---
If open_ios() fails, then tracer_wait_unblock() in the
thread_main() waits for event, wich will never occur:
in the case of unsuccess tracers are not unblocked.
Fixup:
---
Make sure unblock_tracers() is also called in the case on
unsuccess (when nthreads_running != ncpus).
The patch has been sent to upstream:
http://marc.info/?l=linux-btrace&m=127859567318806&w=2
Milos, can you justify this as a blocker (i.e., would you hold up the RHEL6.0 release for this specific fix?), or should be move this back to 6.1?
Thanks!
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/RHBA-2011-0718.html