Closed
Bug 970562
Opened 10 years ago
Closed 10 years ago
[Gonk][seccomp] seccomp violation: __NR_sched_getscheduler
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfletcher, Assigned: jld)
References
Details
Attachments
(1 file)
833 bytes,
patch
|
kang
:
review+
|
Details | Diff | Splinter Review |
When using the Camera app to take a picture, we get the following seccomp violation: E/Sandbox ( 2013): seccomp sandbox violation: pid 2013, syscall 157, args 0 0 1 0 5 10000. Killing process. syscall 157 appears to be __NR_sched_getscheduler Device: Nexus 4 Branch: 1.4.0.0-prerelease Git commit info: a504e2e0 Gecko: 893735910eb5db1d9b69575160d0e53d3be7402a Gaia: a504e2e01335167275e47f35ddc5b89bb858a892
Comment 1•10 years ago
|
||
Note taking pictures seems to be ok on Buri, probably something nexus specific?
Reporter | ||
Comment 3•10 years ago
|
||
I also get this seccomp violation when I try to send SMS messages
Assignee | ||
Comment 4•10 years ago
|
||
(In reply to Rob Fletcher [:omerta] from comment #0) > Gecko: 893735910eb5db1d9b69575160d0e53d3be7402a That version has the patches that should give us a minidump for seccomp violations. (Reproducing with gdb attached also works, and might be easier if it's a local build.)
Assignee | ||
Comment 5•10 years ago
|
||
Incidentally, we already have sched_setscheduler (as well as sched_get_priority_m{in,ax}), so adding sched_getscheduler to the whitelist in gecko/security/sandbox/linux/seccomp_filter.h shouldn't be a problem.
Assignee | ||
Comment 6•10 years ago
|
||
Tested on Nexus 4.
Assignee: nobody → jld
Attachment #8380065 -
Flags: review?(gdestuynder)
Attachment #8380065 -
Flags: review?(gdestuynder) → review+
Assignee | ||
Comment 7•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/b52309ff5fe7
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b52309ff5fe7
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•