Bug 1731336
Summary: | svsematest command report error "Could not access /sys/kernel/debug/tracing/tracing_enabled" | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Qiao Zhao <qzhao> | ||||
Component: | rt-tests | Assignee: | John Kacur <jkacur> | ||||
Status: | CLOSED ERRATA | QA Contact: | Chang Yin <cyin> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 8.1 | CC: | bhu, cyin, rt-maint | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-11-05 20:35:58 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1696402 | ||||||
Attachments: |
|
Description
Qiao Zhao
2019-07-19 07:27:27 UTC
I draft a patch and test passed. Please review. For current RHEL7 and RHEL8, we use tracing_on to control tracing disable/enable. The tracing_enabled is not the correct value. diff --git a/src/svsematest/svsematest.c b/src/svsematest/svsematest.c index dfa4660..a265d90 100644 --- a/src/svsematest/svsematest.c +++ b/src/svsematest/svsematest.c @@ -187,7 +187,7 @@ void *semathread(void *param) char tracing_enabled_file[MAX_PATH]; strcpy(tracing_enabled_file, get_debugfileprefix()); - strcat(tracing_enabled_file, "tracing_enabled"); + strcat(tracing_enabled_file, "tracing_on"); int tracing_enabled = open(tracing_enabled_file, O_WRONLY); if (tracing_enabled >= 0) { Created attachment 1595128 [details]
change tracing_enabled to tracing_on where needed
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:3308 |