diff options
| author |   Dmitry Osipenko <dmitry.osipenko@collabora.com> | 2023-05-30 01:39:31 +0300 |
|---|---|---|
| committer | Dmitry Osipenko <dmitry.osipenko@collabora.com> | 2023-06-21 20:22:20 +0300 |
| commit | 30b5144ca41266ffc6071c33eea4076b66ac5eb9 (patch) | |
| tree | 3ebcf7ce1ae8b40ae9c8f97704184242ef7fd729 /drivers/dma-buf/Kconfig | |
| parent | media: videobuf2: Don't assert held reservation lock for dma-buf mmapping (diff) | |
| download | wireguard-linux-30b5144ca41266ffc6071c33eea4076b66ac5eb9.tar.xz wireguard-linux-30b5144ca41266ffc6071c33eea4076b66ac5eb9.zip | |
dma-buf/heaps: Don't assert held reservation lock for dma-buf mmapping
Don't assert held dma-buf reservation lock on memory mapping of exported
buffer.
We're going to change dma-buf mmap() locking policy such that exporters
will have to handle the lock. The previous locking policy caused deadlock
problem for DRM drivers in a case of self-imported dma-bufs once these
drivers are moved to use reservation lock universally. The problem
solved by moving the lock down to exporters. This patch prepares dma-buf
heaps for the locking policy update.
Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230529223935.2672495-3-dmitry.osipenko@collabora.com
Diffstat (limited to 'drivers/dma-buf/Kconfig')
0 files changed, 0 insertions, 0 deletions