Assuming these crashes show up in crash-stats.mozilla.com, are there particular signatures, metadata, or other patterns that would let us say "this crash is caused by a sandbox failure"?
That seems like it would be fairly important, so that we can monitor this in the field. --BDS On Tue, Jul 5, 2016 at 5:11 PM, Paul Theriault <ptheria...@mozilla.com> wrote: > > > On 6 Jul 2016, at 3:39 AM, Steve Fink <sf...@mozilla.com> wrote: > > > > On 07/05/2016 01:33 AM, Julian Hector wrote: > >> If you encounter a crash that may be due to seccomp, please file a bug > in > >> bugzilla and block Bug 1280415, we use it to track issues experienced on > >> nightly. > > > > What would such a crash look like? Do they boil down to some system call > returning EPERM? > > > > > FYI for others since the reply was off-list: > --------------------------- > It is a crash of the content process, and somewhere in the logs you should > find an entry similar to this: > > "Sandbox: seccomp sandbox violation: pid 5154, syscall 355, args > 2620711623 0 0 0 3012860244 3077481872. Killing process." > > You could also check by setting: security.sandbox.content.level = 0 and > see if the problem still exists. > --------------------------- > There is also a wiki page with more information from b2g that has some > information. > https://wiki.mozilla.org/Security/Sandbox/Seccomp#Use_in_Gecko > > We will update to make this Linux specific instead of b2g. > > Thanks, > Paul > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
