On Tue, 14 Jul 2020 at 13:14, Felix Kuehling <Felix.Kuehling@xxxxxxx> wrote: > > This allows exporting and importing buffers. The API generates handles > that can be used with the HIP IPC API, i.e. big numbers rather than > file descriptors. First up why? I get the how. > + * @share_handle is a 128 bit random number generated with > + * @get_random_bytes. This number should be very hard to guess. > + * Knowledge of the @share_handle implies authorization to access > + * the shared memory. User mode should treat it like a secret key. > + * It can be used to import this BO in a different process context > + * for IPC buffer sharing. The handle will be valid as long as the > + * underlying BO exists. If the same BO is exported multiple times, Do we have any examples of any APIs in the kernel that operate like this? That don't at least layer some sort of file permissions and access control on top? The reason fd's are good is that combined with unix sockets, you can't sniff it, you can't ptrace a process and find it, you can't write it out in a coredump and have someone access it later. To me this isn't secure design, it's obscure design, now I get to find you've likely shipped this in "downstream" ROCm already, and have customers running it. Maybe someone who knows security can ack merging this sort of uAPI design, I'm not confident in what it's doing is in any ways a good idea. I might have to ask some people to take a closer look. Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
