Running tests on try with seccomp enabled, hit a seccomp violation when executing the system call: sys_rt_tgsigqueueinfo. tgsigqueueinfo, allows to send signals and data to another process which is probably pretty dangerous to allow. I haven't investigated it further, but all e10s tests seem to fail without this system call in the seccomp whitelist.
I know it is kind of dangerous to allow this syscall, but our main focus now is getting seccomp enabled, so I would say we whitelist it for now. Try push for build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a533af28e323
Comment on attachment 8757409 [details] [diff] [review] Add sys_rt_tgsigqueueinfo to seccomp whitelist r=jld You should be able to restrict this to same-process use, the same way as for tgkill.
Thanks Jed for the feedback, I applied the same restriction as with tgkill. Try push for build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a8aedb12406f
Attachment #8761142 - Flags: review?(jld) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/de2100437304 Add sys_rt_tgsigqueueinfo to seccomp whitelist r=jld
You need to log in before you can comment on or make changes to this bug.