Branch: refs/heads/release-2.5
Home: https://github.com/seccomp/libseccomp
Commit: d1482eaf5a3643f73bc7f599876e7000c502b3d5
https://github.com/seccomp/libseccomp/commit/d1482eaf5a3643f73bc7f599876e7000c502b3d5
Author: Paul Moore <[email protected]>
Date: 2020-08-19 (Wed, 19 Aug 2020)
Changed paths:
M src/arch-arm.c
M src/arch-mips.c
M src/arch-mips64.c
M src/arch-mips64n32.c
M src/arch-x32.c
Log Message:
-----------
arch: ensure we don't "munge" pseudo syscall numbers
A number of arches/ABIs have either syscall offsets (the MIPS
family) or specific bits (x32) which are applied to their normal
syscall numbers. We generally handle that via "munging" in
libseccomp, and it works reasonably well. Unfortunately we were
applying this munging process to the negative pseudo syscall
numbers as well and this was causing problems.
This patch fixes the various offset/bit arches/ABIs by not applying
the munging to the negative pseudo syscall numbers.
This resolves GH issue #284:
* https://github.com/seccomp/libseccomp/issues/284
Reported-by: Harald van Dijk <[email protected]>
Acked-by: Tom Hromatka <[email protected]>
Signed-off-by: Paul Moore <[email protected]>
(imported from commit 34cde704979defcbddb8eea64295acf0e477c250)
--
You received this message because you are subscribed to the Google Groups
"libseccomp" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/libseccomp/seccomp/libseccomp/push/refs/heads/release-2.5/1db3b3-d1482e%40github.com.
