Bug 1195839
| Summary: | no execveat in rhel6 kernel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Cermak <mcermak> |
| Component: | systemtap | Assignee: | Frank Ch. Eigler <fche> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.7 | CC: | emajorsi, mcermak, mjw, scox |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | systemtap-2.7-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
The systemtap's system call tapset-library unconditionally included support for the "execveat" system call, even though "execveat" did not exist in Red Hat Enterprise Linux 6 kernels. Consequently, system call probing scripts could fail with a semantic error. With this update, "execveat" is treated conditionally, and the scripts no longer fail in this situation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-22 06:45:12 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: | |||
Verified against systemtap-2.7-2.el6. Covered by upstream testsuite. 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://rhn.redhat.com/errata/RHBA-2015-1333.html |
The rhel6 kernel (2.6.32-536.el6) doesn't have the execveat syscall. Due to this [nd]_syscalls-detailed.stp fails: ======= Running ./buildok/syscalls-detailed.stp starting ./buildok/syscalls-detailed.stp spawn2 ./buildok/syscalls-detailed.stp spawn ./buildok/syscalls-detailed.stp semantic error: while resolving probe point: identifier 'syscall' at ./buildok/syscalls-detailed.stp:345:7 source: probe syscall.execveat, syscall.compat_execveat ? ^ semantic error: no match Pass 2: analysis failed. [man error::pass2] ======= Please, backport upstream commit 86c7acd.