@@ -23,10 +23,20 @@ dynamic and can be hot-reloaded when the new policy validates successfully.
2323
2424Before applying Landlock, the supervisor enriches baseline filesystem paths that
2525the runtime needs. Missing baseline paths are skipped so one absent runtime path
26- does not weaken the whole ruleset. When GPU devices are present, GPU baseline
27- enrichment adds existing GPU device nodes as read-write paths and promotes
28- ` /proc ` to read-write because CUDA workloads write thread metadata under
29- ` /proc/<pid>/task/<tid>/comm ` .
26+ does not weaken the whole ruleset. When GPU devices are present without a CDI
27+ context, GPU baseline enrichment adds existing GPU device nodes as read-write
28+ paths. GPU sandboxes with CDI context use CDI-derived paths instead of the
29+ hard-coded GPU baseline. Both paths promote ` /proc ` to read-write because CUDA
30+ workloads write thread metadata under ` /proc/<pid>/task/<tid>/comm ` .
31+
32+ GPU/CDI sandboxes can also carry a supervisor-only CDI context from the compute
33+ driver. The supervisor resolves selected CDI IDs from mounted CDI specs and
34+ adds derived device nodes, library mount destinations, and supplemental GIDs
35+ before agent exec. CDI host paths are ignored for policy. Derived mount
36+ destinations default to read-only; writable CDI single-file mounts require an
37+ exact ` filesystem_policy.read_write ` opt-in, and writable CDI directory mounts
38+ fail closed. CDI resolution errors are security-relevant startup failures and
39+ emit OCSF findings.
3040
3141Landlock rules are tailored to the inode type reported by the already-opened
3242path descriptor. Directories retain the requested directory and file rights;
0 commit comments