fd820e76e4
In some cases userspace may need to create dmabuffers from userspace on such example is the software ISP part of libcamera which needs to allocate dma-buffers for the output of the software ISP. At first the plan was to allow console users access to /dev/dma_heap/*, this was discussed with various kernel folks here: https://lore.kernel.org/all/bb372250-e8b8-4458-bc99-dd8365b06991@redhat.com/ Giving console users access to the dma_heap's was deemed a bad idea because memory allocated this way is not accounted in cgroup limits. Giving access to /dev/udmabuf OTOH was deemed acceptable so that is what this patch adds. Resolves: #32662
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack