Loading
Bug 1698778 - Loosen the RDD sandbox policy to support VA-API (including Intel VCS2). r=gcp
Changes: 1. For the `intel` drivers [on newer hardware][VCS2], access to SysV IPC is granted. There is a slight restriction: `semget` and `shmget` are restricted to the fixed `key_t` value used by the driver; however, the other calls take shm/sem identifiers, which are dynamically assigned and globally scoped, so an attacker could still access other resources. This is considered a reasonable tradeoff for not needing to allow this (or, eventually, any GPU access) in the content process, which is much easier for malicious content to attack than RDD. 2. Access to devices in `/dev/dri` and the `DRM_IOCTL_*` ioctls (type `'d'`). 3. Read access to the parts of sysfs used by Mesa to do device detection; again, given the choice we'd rather allow this in RDD than content. 4. Read access to directories containing libraries, for plugin loading. 5. Allowing `kcmp` in the special case of comparing the process's own fds, for `amdgpu` (already allowed for content). 6. The `eventfd2` syscall, which we use in connection with dma-buf. [VCS2]: https://github.com/intel/media-driver/blob/77b3b2a6c366/media_driver/linux/common/os/mos_os_specific.c#L1508-L1512 Differential Revision: https://phabricator.services.mozilla.com/D131680