Closed Bug 941375 Opened 11 years ago Closed 11 years ago

TBPL should be able to usefully report on sandbox violations

Categories

(Core :: Security, defect)

Product:
Core
Component:
Security
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla30

People

(Reporter: jld, Assigned: jld)

References

Details

(Keywords: meta)

When we have targets in TBPL that use seccomp sandboxing, there will eventually be test runs that fail due to sandbox violation. We need to ensure that the responsible developer, and the sheriffs, can get enough information about the failure to take appropriate action. In particular, tossing a line into logcat and exiting, so that the test times out five minutes later, is probably not that. It seems to me that we should be able to handle SIGSYS (caused by a sandbox failure in reporter mode) the same way we'd handle a SIGSEGV from a memory error.
Making the Breakpad reporter handle SIGSYS turns out to be fairly simple. There's a bit of subtlety in making it coexist with the existing reporter handler, and dealing with signal handler return being different from the other crash signals, but nothing huge.
Assignee: nobody → jld
Depends on: 942407
Depends on: 943774
Depends on: 945330
Depends on: 945498
Depends on: 945504
There are enough sub-bugs now that having patches on this bug itself seemed potentially confusing.
Keywords: meta
It's not ideal yet (see bug 942290), but it seems to be “useful”.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in before you can comment on or make changes to this bug.