Closed
Bug 1422198
Opened 7 years ago
Closed 6 years ago
Log something from the sandbox file broker if sendmsg()ing the response fails
Categories
(Core :: Security: Process Sandboxing, enhancement, P2)
Tracking
()
RESOLVED
FIXED
mozilla59
Tracking | Status | |
---|---|---|
firefox59 | --- | fixed |
People
(Reporter: jld, Assigned: jld)
References
Details
Attachments
(1 file)
(In reply to Jed Davis [:jld] (⏰UTC-7) from bug 1420475 comment #4) > That error message means that the broker closed the request's response > socket without sending a response. The interesting thing is that there's no > accompanying message from the broker (cf., for example, bug 1401774). This > is in the middle of a test run, so it's not because of racing with parent > process shutdown. So the only case that's left is where sendmsg()ing the > response fails (and, yes, EINTR is handled). So let's log something in that case. Worst case, we'll somtimes get a spurious message about ECONNRESET or ESPIPE or something if the content process exits concurrently with an open(), but those should be easy to distinguish from actual problems (and they aren't something that the test harness will consider a failure).
Updated•7 years ago
|
Priority: -- → P2
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 3•6 years ago
|
||
mozreview-review |
Comment on attachment 8935900 [details] Bug 1422198 - Log about failure to send a sandbox broker reply. https://reviewboard.mozilla.org/r/206774/#review213682
Attachment #8935900 -
Flags: review?(gpascutto) → review+
Pushed by jedavis@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d857200d4596 Log about failure to send a sandbox broker reply. r=gcp
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d857200d4596
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox59:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in
before you can comment on or make changes to this bug.
Description
•