You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(sandbox): ioprio_set is denied for every target, so ionice on the caller's own process fails #5706
I run OpenShell sandboxes with the Podman and Kubernetes drivers and I work on the sandbox isolation core. This came out of the review of #5212. I found it by reading the code and have not hit it in production.
Problem Statement
crates/openshell-sandbox/src/linux/child_seccomp.rs denies ioprio_set for every target. A workload cannot change its own I/O priority, so ionice -p $$ and ionice -c3 <command> fail with EPERM, although they work in a plain container. It is the same gap #5185 covers for sched_set*, prlimit64, and setpriority, and #5212 leaves it out of scope.
Impact / Why This Matters
Build and batch tooling that lowers its own I/O priority (ionice, psutil ionice()) fails only under OpenShell. The only workaround is to drop the call from the workload.
Acceptance Criteria
ioprio_set(IOPRIO_WHO_PROCESS, 0, ...) and the caller's own PID or sibling TIDs are allowed.
Other targets, IOPRIO_WHO_PGRP, and IOPRIO_WHO_USER stay denied with EPERM.
Activity