Bug 1565773 - rebase systemtap in RHEL 7.6
Summary: rebase systemtap in RHEL 7.6
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemtap
Version: 7.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Frank Ch. Eigler
QA Contact: Martin Cermak
Vladimír Slávik
Depends On: 1311586
Blocks: 1505884
TreeView+ depends on / blocked
Reported: 2018-04-10 18:20 UTC by David Smith
Modified: 2018-10-30 10:47 UTC (History)
7 users (show)

Fixed In Version: systemtap-3.3-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
_systemtap_ rebased to version 3.3 The _systemtap_ packages have been upgraded to upstream version 3.3, which provides a number of bug fixes and enhancements: * Limited support for the extended Berkeley Packet Filter (eBPF) tracing on the Intel64 and AMD64 architectures has been added. Use the `--runtime=bpf` option to use eBPF as a backend. Due to numerous limitations of `eBPF` and its SystemTap interface, only simple scripts work. For more information, see the Knowledge article https://access.redhat.com/articles/3550581 and the stapbpf(8) manual page. * The `--sysroot` option has been optimized for cross-compiled environments. * A new `--example` option allows you to search the example scripts distributed with SystemTap without providing the whole path of the file. * The SystemTap runtime and tapsets are compatible with kernel versions up to 4.17. * Usage of SystemTap on systems with real time kernel or machines with a high number of CPUs has been improved. * Handling of code used for Spectre and Meltdown attack mitigation has been improved.
Clone Of:
Last Closed: 2018-10-30 10:46:00 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3168 0 None None None 2018-10-30 10:47:19 UTC

Description David Smith 2018-04-10 18:20:49 UTC
We plan to incorporate soon to be released upstream systemtap into RHEL 7.6.

Comment 12 errata-xmlrpc 2018-10-30 10:46: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.


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