Paul Chaignon's GSoC status report - #4 of 12

[Dmitry V. Levin]

On Mon, Jun 24, 2019 at 09:12:12PM +0200, Paul Chaignon wrote:
[...]
> - While going through the patched test suite (see previous GSoC report), I
>   noticed that several tests with fork() or threads but without the -f option
>   were failing.  These are failing because children tasks inherit the seccomp
>   filter of parent tasks.  Thus, if tracing a multi-task process with strace -n
>   (i.e., seccomp filtering enabled), we should make sure that -f is enabled so
>   that all tasks have a proper tracer.  The current patchset errors out when -n
>   is given without -f.  While this propagation of seccomp filters to children
>   tasks makes sense for sandboxing, it might be worth having an option in the
>   kernel to disable propagation for tracing use cases.  Without such an option
>   in the Linux API, strace will only be able to use seccomp filtering when -f
>   is set.  What do you think?  Should I send an RFC patch to the kernel after
>   my main seccomp tasks are finished?

What kind of Linux API change do you have in mind?
A new SECCOMP_FILTER_FLAG_* flag for SECCOMP_SET_MODE_FILTER?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20190625/94989485/attachment.bin>