BUG: fix s390/s390x handling of shm* syscalls #206
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #193 exposed a few cases where libseccomp isn't completely supporting
shm*()
syscalls on s390/s390x. This commit adds IPC support forshmat()
,shmdt()
,shmget()
, andshmctl()
. Socket support for the aforementioned syscalls was unchanged and should still work as before.I ran this through
arch-syscall-validate
, but I really don't have a way to test these changes. @cpaelzer or others - do you have a way to test this?