Crash reports show that sys_get_mempolicy is called from the content process: https://crash-stats.mozilla.com/search/?product=Firefox&reason=~SIGSYS&address=0xef&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports
This is used by ffmpeg / libavcodec to decide the thread pool strategy for H264/H265 decoding. It's harmless but on the other hand it's also pointless attack surface.
Created attachment 8774437 [details] [diff] [review] Add sys_get_mempolicy to seccomp whitelist. r=gcp Try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=c6f75781c4fc
Assignee: nobody → julian.r.hector
Status: NEW → ASSIGNED
Attachment #8774437 - Flags: review?(gpascutto)
Attachment #8774437 - Flags: review?(gpascutto) → review+
Try in Comment 2. Please check-in after Bug 1285770 (to avoid merge conflicts)
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/c941e8a13954 Add sys_get_mempolicy to seccomp whitelist. r=gcp
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox50: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
You need to log in before you can comment on or make changes to this bug.