Bug 1770693
| Summary: | Rebase libseccomp to the latest upstream version 2.4.3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marek Tamaskovic <mtamasko> |
| Component: | libseccomp | Assignee: | Radovan Sroka <rsroka> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Zelený <mzeleny> |
| Severity: | medium | Docs Contact: | lmcgarry |
| Priority: | medium | ||
| Version: | 8.2 | CC: | coli, dapospis, juzhang, lmanasko, mzeleny, rsroka, tjaros |
| Target Milestone: | rc | Keywords: | Rebase, Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libseccomp-2.4.3-1.el8 | Doc Type: | Enhancement |
| Doc Text: |
.The `libseccomp` library has been rebased to version 2.4.3
The `libseccomp` library, which provides an interface to the `seccomp` system call filtering mechanism, has been upgraded to version 2.4.3.
This update provides numerous bug fixes and enhancements. Notable changes include:
* Updated the `syscall` table for Linux v5.4-rc4.
* No longer defining `pass:[__NR_x]` values for system calls that do not exist.
* `pass:[__SNR_x]` is now used internally.
* Added `define` for `pass:[__SNR_ppoll]`.
* Fixed a multiplexing issue with s390/s390x shm* system calls.
* Removed the `static` flag from the `libseccomp` tools compilation.
* Added support for `io-uring` related system calls.
* Fixed the Python module naming issue introduced in the v2.4.0 release; the module is named `seccomp` as it was previously.
* Fixed a potential memory leak identified by `clang` in the `scmp_bpf_sim` tool.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 01:42:40 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: | |||
|
Description
Marek Tamaskovic
2019-11-11 08:01:37 UTC
Updated following peer review. 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 (libseccomp 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/RHEA-2020:4472 |