Automated test for crash reporting for seccomp-bpf policy violations

NEW
Unassigned

Status

()

defect
P3
normal
3 years ago
2 years ago

People

(Reporter: jld, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
Unspecified
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox50 affected)

Details

(Whiteboard: sb+)

Once seccomp-bpf is stable on desktop, we'll have an opportunity to establish automated testing for the SIGSYS crash reporting.

I'd have preferred to get testing in place back when the sandbox crash reporter integration first landed for B2G, but B2G had only mochitest-plain, which isn't good for tests that crash the entire content process.  However, as pointed out by :ted on mozilla.dev.platform, on desktop there are browser-chrome tests that cover content process crash reporting and collection[1], and there's even a utility function for this kind of test.  Currently it uses ctypes to dereference a bad pointer, but it could be modified to take an arbitrary frame script; invoking syscall(4000) should do the trick.


[1]: https://dxr.mozilla.org/mozilla-central/search?q=path%3Abrowser_*crash
[2]: https://dxr.mozilla.org/mozilla-central/rev/70e05c6832e831374604ac3ce7433971368dffe0/testing/mochitest/BrowserTestUtils/BrowserTestUtils.jsm#758

Updated

3 years ago
Whiteboard: sb+

Updated

2 years ago
Priority: -- → P3

Updated

2 years ago
Blocks: sb-test
You need to log in before you can comment on or make changes to this bug.