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 1455514 - Enable provide_yama_scope for rhel >= 7.4
Summary: Enable provide_yama_scope for rhel >= 7.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: elfutils
Version: 7.3
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: rc
: ---
Assignee: Mark Wielaard
QA Contact: qe-baseos-tools-bugs
Marie Hornickova
URL:
Whiteboard:
Depends On:
Blocks: 1367855
TreeView+ depends on / blocked
 
Reported: 2017-05-25 11:59 UTC by Steve Grubb
Modified: 2017-08-01 22:06 UTC (History)
7 users (show)

Fixed In Version: elfutils-0.168-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:06:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2020 0 normal SHIPPED_LIVE elfutils bug fix update 2017-08-01 19:31:43 UTC

Description Steve Grubb 2017-05-25 11:59:48 UTC 
Description of problem:
The RHEL 7.4 kernel provides the yama.ptrace_scope sysctl. We need to enable the provide_yama_scope variable in the elfutils package so that systemd can set the sysctl to 0. The kernel defaults to 1 which is not what we want.

Version-Release number of selected component (if applicable):
elfutils-0.168-6.el7
Comment 1 Mark Wielaard 2017-05-25 12:19:10 UTC 
A patch to the elfutils spec to do that is easy enough:

diff --git a/elfutils.spec b/elfutils.spec
index c710540..e5bd050 100644
--- a/elfutils.spec
+++ b/elfutils.spec
@@ -9,7 +9,7 @@ Group: Development/Tools
 
 Release: %{baserelease}%{?dist}
 
-%global provide_yama_scope     0
+%global provide_yama_scope     1
 
 %if 0%{?fedora}
 %global provide_yama_scope     (%fedora >= 22)

That will build elfutils-default-yama-scope-0.168-6.el7.noarch.rpm which installs the /usr/lib/sysctl.d/10-default-yama-scope.conf file (defaults to 0) and provides "default-yama-scope". Which systemd will pull in indirectly through its dependency on elfutils-libs.

Because this introduces a new subpackage elfutils-default-yama-scope are there any extra procedures to follow to get it into the default repository or is patching the spec and building a new elfutils enough?
Comment 2 Mark Wielaard 2017-05-25 12:28:21 UTC 
One comment (and adding Lukas Vrabec who fixed it in Fedora).
When we introduced this in Fedora we hit a selinux issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1253926
"SELinux is preventing /usr/lib/systemd/systemd-sysctl from using the 'sys_ptrace' capabilities."
We should double check that is already fixed in rhel7.4 selinux.
Comment 4 Steve Grubb 2017-05-25 17:16:54 UTC 
The question about selinux policy is being checked. If any change is needed, a new bz will be opened and set to block this bz. Thanks.
Comment 15 errata-xmlrpc 2017-08-01 22:06:37 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/RHEA-2017:2020
Note You need to log in before you can comment on or make changes to this bug.