Bug 1810216

Summary:	"ftrace" logging tapset not working as expected in RHEL-7 and RHEL-8
Product:	Red Hat Enterprise Linux 7	Reporter:	Apoorv Verma <apverma>
Component:	systemtap	Assignee:	Frank Ch. Eigler <fche>
Status:	CLOSED ERRATA	QA Contact:	Martin Cermak <mcermak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.8	CC:	dsmith, lberk, mcermak, mjw, onatalen, smakarov
Target Milestone:	rc	Keywords:	Patch, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	systemtap-4.0-13.el7	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-29 19:46:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 4 Frank Ch. Eigler 2020-03-05 12:21:55 UTC

Thanks, merged!

commit ffb40c659a690f4341e43051f6d5114732b3fe46
Author: Frank Ch. Eigler <fche>
Date:   Thu Mar 5 07:17:04 2020 -0500

    RHBZ1810216: fix ftrace() tapset function related autoconf test
    
    It was reported that the ftrace() tapset function stopped working at
    some point - due to an autoconf-* false negative.  We failed to notice
    because the tapset function was quietly mapped to a nop in this case.
    Now ftrace() will #error in -p4 if autoconf doesn't detect a suitable
    kernel facility.  A forked testcase buildok/logging-embedded2.stp
    checks for it.
    
    Suggested-by: Oleksandr Natalenko <onatalen>

Comment 13 errata-xmlrpc 2020-09-29 19:46:24 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 (systemtap bug fix and enhancement update), 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-2020:3891