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 583624 - blktrace does not kill a running trace via -k
Summary: blktrace does not kill a running trace via -k
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: blktrace
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Edward Shishkin
QA Contact: Milos Malik
URL:
Whiteboard:
: 598647 624480 (view as bug list)
Depends On: 513950
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-19 09:19 UTC by Milos Malik
Modified: 2018-11-14 15:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 513950
Environment:
Last Closed: 2011-10-04 13:09:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Milos Malik 2010-04-19 09:19:26 UTC 
Reproducable with blktrace-1.0.1-3.1.el6 on machine with RHEL6.0-20100417.n.0.
Comment 2 RHEL Program Management 2010-04-19 09:38:05 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 Edward Shishkin 2010-06-24 16:18:37 UTC 
The mainline fixup:
http://marc.info/?l=linux-btrace&m=127177005524997&w=2
Comment 5 Edward Shishkin 2010-06-24 16:32:52 UTC 
*** Bug 598647 has been marked as a duplicate of this bug. ***
Comment 6 RHEL Program Management 2010-07-15 15:09:54 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 8 Eric Sandeen 2010-10-29 21:36:05 UTC 
Sending blktrace bugs over to Edward, as he did the upstream work for them.
Comment 9 Edward Shishkin 2010-11-01 19:30:28 UTC 
*** Bug 624480 has been marked as a duplicate of this bug. ***
Comment 14 Suzanne Logcher 2011-03-28 19:25:25 UTC 
Unfortunately this issue could not be fixed in RHEL 6.1.
It has been moved to RHEL 6.2.
Comment 15 Ric Wheeler 2011-06-09 15:53:11 UTC 
Edward, Eric, did blktrace get into the approved component list for 6.2?

If so, let's fix this or move it back to 6.3.

Thanks!
Comment 16 Edward Shishkin 2011-06-09 16:32:03 UTC 
This is not a critical issue, and an additional
patch should be sent to upstream, so I guess, to 6.3
Comment 23 IBM Bug Proxy 2011-09-28 06:52:11 UTC 
------- Comment From vahegde1.ibm.com 2011-09-28 02:44 EDT-------
Hi Red Hat,

Any update on this bug ? Will this be considered in 6.2 cycle ?

Thanks
Vasant
Comment 26 Edward Shishkin 2011-10-04 13:09:01 UTC 
Closed as upstream doesn't consider this as a bug:
they prefer to have undocumented option "-k" as a
"rough edge" for their internal needs (not to kill
running trace):
http://marc.info/?l=linux-btrace&m=131245973528087&w=2

Since this option in not documented, users are not
supposed to use it.

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