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 1658332 - eBPF tool 'biolatency -D' fails with Traceback
Summary: eBPF tool 'biolatency -D' fails with Traceback
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: bcc
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.1
Assignee: Jerome Marchand
QA Contact: Ziqian SUN (Zamir)
URL:
Whiteboard:
Depends On: 1680631
Blocks: 1645899 1701002
TreeView+ depends on / blocked
 
Reported: 2018-12-11 19:12 UTC by John Pittman
Modified: 2019-11-05 20:42 UTC (History)
8 users (show)

Fixed In Version: 0.8.0-1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:42:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
biolatency -D command output (3.25 KB, text/plain)
2018-12-11 19:12 UTC, John Pittman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3749701 0 None None None 2018-12-11 19:42:00 UTC
Red Hat Product Errata RHBA-2019:3327 0 None None None 2019-11-05 20:42:32 UTC

Description John Pittman 2018-12-11 19:12:02 UTC
Created attachment 1513488 [details]
biolatency -D command output

Description of problem:

eBPF tool 'biolatency -D' fails with Traceback

Traceback (most recent call last):
  File "./biolatency", line 121, in <module>
    fn_name="trace_req_completion")
  File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 592, in attach_kprobe
    fn = self.load_func(fn_name, BPF.KPROBE)
  File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 377, in load_func
    (func_name, errstr))
Exception: Failed to load BPF program b'trace_req_completion': Permission denied

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

kernel-4.18.0-40.el8.x86_64
bcc-tools-0.7.0-3.el8.x86_64
bcc-0.7.0-3.el8.x86_64

Steps to Reproduce:

Install RHEL8 beta on KVM virt
Install bcc/bcc-tools
cd /usr/share/bcc/tools
./biolatency -D

Actual results:

Command fails

Expected results:

Command should succeed

Comment 1 Jerome Marchand 2018-12-12 09:39:58 UTC
Looks like we need commit fc245dfe9dab ("biolatency: Fix --disks bpf_probe_read() (#1980)")

Comment 11 errata-xmlrpc 2019-11-05 20:42:19 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://access.redhat.com/errata/RHBA-2019:3327


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