diff options
| author |   Dave Airlie <airlied@redhat.com> | 2020-04-08 09:14:21 +1000 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2020-04-08 09:14:34 +1000 |
| commit | 3208a24f2ba2e666908619d51173ca62b08f3a75 (patch) | |
| tree | e17f34a89490f0f845ceb735926514f7abff196a /drivers/dma-buf | |
| parent | Merge tag 'drm-intel-next-fixes-2020-04-02' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (diff) | |
| parent | drm/mm: revert "Break long searches in fragmented address spaces" (diff) | |
| download | wireguard-linux-3208a24f2ba2e666908619d51173ca62b08f3a75.tar.xz wireguard-linux-3208a24f2ba2e666908619d51173ca62b08f3a75.zip | |
Merge tag 'drm-misc-next-fixes-2020-04-04' of git://anongit.freedesktop.org/drm/drm-misc into drm-next
A bunch of fixes to avoid null pointer dereference in fbcon, fix a return
in xen, some DT bindings fixes, a vc4 issue with 1920x1200 mode validation,
and a conflicting framebuffer in vboxvideo.
Signed-off-by: Dave Airlie <airlied@redhat.com>
From: Maxime Ripard <maxime@cerno.tech>
Link: https://patchwork.freedesktop.org/patch/msgid/20200404090057.a3m7uw6tavwtcyon@gilmour.lan
Diffstat (limited to 'drivers/dma-buf')
| -rw-r--r-- | drivers/dma-buf/Kconfig | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig index ef73b678419c..9626673f1d83 100644 --- a/drivers/dma-buf/Kconfig +++ b/drivers/dma-buf/Kconfig @@ -43,11 +43,12 @@ config DMABUF_MOVE_NOTIFY bool "Move notify between drivers (EXPERIMENTAL)" default n help - Don''t pin buffers if the dynamic DMA-buf interface is available on both the - exporter as well as the importer. This fixes a security problem where - userspace is able to pin unrestricted amounts of memory through DMA-buf. - But marked experimental because we don''t jet have a consistent execution - context and memory management between drivers. + Don't pin buffers if the dynamic DMA-buf interface is available on + both the exporter as well as the importer. This fixes a security + problem where userspace is able to pin unrestricted amounts of memory + through DMA-buf. + This is marked experimental because we don't yet have a consistent + execution context and memory management between drivers. config DMABUF_SELFTESTS tristate "Selftests for the dma-buf interfaces" |