Allowing sync(2) is technically a violation of Capsicum's "no global namespace access" requirement, but sync does not leak or modify user- visible state.
Details
Details
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
| sys/kern/syscalls.master | ||
|---|---|---|
| 340 | ||
Comment Actions
Seems reasonable. I do wonder if there are any side channels related for forced I/O, but I doubt they are interesting vs e.g., things you can do with CPU load.