Oh, and here's the output from strace: https://pastebin.com/spnwDJtN
Notice the "Invalid argument" from seccomp and that the `fork` syscall
is not visible at all. If I add a filter on `clone` instead, the process
is properly killed.
Is this a bug I should report on GitHub?
On 06.07.2017 10:07, Marcin Mielniczuk wrote:
Hi!
I'm playing around with libseccomp and I'm trying to filter just the
fork function, for the time being. I came up with the following simple
code:
https://pastebin.com/FxRzAuLz
Even though no errors are returned, the fork call is not interecepted
and the process is not killed.
Am I doing something wrong?
Arch Linux, kernel 4.9.35, gcc 7.1.1, glibc 2.25, libseccomp 2.3.2.
Thanks!
--
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
