Closed Bug 1647957 Opened 4 years ago Closed 3 years ago

Allow RDD and Socket processes to read `/proc/self/{statm,smaps}` on Linux

Categories

(Core :: Security: Process Sandboxing, defect, P1)

defect

Tracking

()

RESOLVED FIXED
90 Branch
Tracking Status
firefox90 --- fixed

People

(Reporter: n.nethercote, Assigned: gerard-majax)

References

Details

Attachments

(1 file)

As per bug 1198552, memory reporting currently relies on reading /proc/self/statm and /proc/self/smaps on Linux. This is allowed in content processes and the GPU process, but isn't allowed in the RDD process or the Socket process.

This means that memory reporting of RDD and Socket processes is missing some important measurements, and this leads to some test failures as seen in bug 1644834.

It would be very helpful if the RDD and Socket processes could be allowed to read these files. I looked at doing this myself, and RDDSandboxPolicy and SandboxBrokerPolicyFactory::GetContentPolicy() seem relevant, but I couldn't quite work out what the changes would look like.

Priority: -- → P1

The severity field is not set for this bug.
:gcp, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gpascutto)
Severity: -- → S3
Flags: needinfo?(gpascutto)
Blocks: 1640105
Assignee: jld → lissyx+mozillians

Tests in bug 1644834 comment 14 were failing locally for me, with the patch on https://treeherder.mozilla.org/jobs?repo=try&revision=6f78b54c292ade32da9bfd729ef68b45323eb1a9 it is passing all three locally

Pushed by alissy@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ee7be8031500
Allow RDD and Socket processes to read /proc/self/{statm,smaps} on Linux r=gcp
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: