Closed Bug 1275781 Opened 5 years ago Closed 5 years ago
Seccomp sandbox violation: sys
_accept called in content process of Firefox desktop
Running tests on try with seccomp enabled  hit a seccomp violation by using sys_accept()  https://treeherder.mozilla.org/#/jobs?repo=try&revision=b74081e971fd&selectedJob=21341876
For now, in order to get seccomp enabled on nightly, I think we should whitelist this and try to figure out later how we can reduce the system calls for the socket API.
Try push for build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=779186042f6f
Attachment #8757321 - Flags: review?(jld) → review+
It looks like this was caused by a test that runs httpd.js in a content process, but only because it needs a custom httpd to run *somewhere*, and it wasn't written with sandboxed e10s in mind. (It also can't ever have worked on B2G.) There should be a followup bug for that.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/25abbc9e6237 Add sys_accept to seccomp whitelist. r=jld
You need to log in before you can comment on or make changes to this bug.