Sandbox: Mount a temporary directory on /dev/shm #1484
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Isolate's default mount rules don't have
norecfor/dev, The host OS has a separate (tmpfs) mount point for/dev/shmwhich is rw and world-writable, so isolate inherits it as rw. This means any solution can write to /dev/shm and communicate with another sandbox. Fix by mounting a fresh tmpfs on /dev/shm.I didn't find this myself, I saw some CMS fork where a commit message mentioned dev/shm, and made a note to investigate it later, and well, turns out it is indeed problematic...
Maybe a better fix is to change the default rules in isolate, to add norec to the /dev rule.