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 1619272 - Provide bpf(2) man page
Summary: Provide bpf(2) man page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: man-pages-overrides
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nikola Forró
QA Contact: Jan Houska
URL:
Whiteboard:
Depends On:
Blocks: 1619614
TreeView+ depends on / blocked
 
Reported: 2018-08-20 13:27 UTC by Stanislav Kozina
Modified: 2018-10-30 11:35 UTC (History)
5 users (show)

Fixed In Version: man-pages-overrides-7.6.2-1.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-30 11:35:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3254 0 None None None 2018-10-30 11:35:13 UTC

Description Stanislav Kozina 2018-08-20 13:27:31 UTC 
With the enablement of eBPF in RHEL-7.6 we also need to ship respective man pages, ie. these two:

./man/man2/bpf.2.gz
./man/man8/bpftool.8.gz
Comment 2 Eugene Syromiatnikov 2018-08-20 13:38:49 UTC 
It's probably also worth updating perf_event_open(2), that contains description of PERF_EVENT_IOC_SET_BPF and PERF_EVENT_IOC_QUERY_BPF.
Comment 3 Nikola Forró 2018-08-21 09:37:40 UTC 
Stanislav,

it seems that bpftool.8 man page is already included in bpftool package.
Comment 7 Jan Houska 2018-08-28 13:08:18 UTC 
VERIFIED

OLD:
man-pages-overrides-7.5.2-1.el7

No output found using  'man 2 bpf' command.


NEW:
man-pages-overrides-7.6.2-1.el7

The command  'man 2 bpf' prints following output:
"""
BPF(2)                                                                          Linux Programmer's Manual                                                                         BPF(2)

NAME
       bpf - perform a command on an extended BPF map or program

SYNOPSIS
       #include <linux/bpf.h>

       int bpf(int cmd, union bpf_attr *attr, unsigned int size);

DESCRIPTION
       The  bpf() system call performs a range of operations related to extended Berkeley Packet Filters.  Extended BPF (or eBPF) is similar to the original ("classic") BPF (cBPF) used .....
"""
Comment 10 errata-xmlrpc 2018-10-30 11:35:04 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-2018:3254
Note You need to log in before you can comment on or make changes to this bug.