[PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Christian König
As we now knew controlling dma_fence synchronization from userspace is extremely dangerous and can not only deadlock drivers but trivially also the whole kernel memory management. Entirely remove this option. We now have in kernel unit tests to exercise the dma_fence framework and it's containers.

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Daniel Vetter
On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: > As we now knew controlling dma_fence synchronization from userspace is > extremely dangerous and can not only deadlock drivers but trivially also the > whole kernel memory management. > > Entirely remove this option. We now have in

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Christian König
Am 29.07.21 um 09:23 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: As we now knew controlling dma_fence synchronization from userspace is extremely dangerous and can not only deadlock drivers but trivially also the whole kernel memory management. Ent

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Daniel Vetter
On Thu, Jul 29, 2021 at 10:38 AM Christian König wrote: > Am 29.07.21 um 09:23 schrieb Daniel Vetter: > > On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: > >> As we now knew controlling dma_fence synchronization from userspace is > >> extremely dangerous and can not only deadlock

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Christian König
Am 29.07.21 um 11:03 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 10:38 AM Christian König wrote: Am 29.07.21 um 09:23 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: As we now knew controlling dma_fence synchronization from userspace is extremely dan

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Daniel Vetter
On Thu, Jul 29, 2021 at 12:21 PM Christian König wrote: > Am 29.07.21 um 11:03 schrieb Daniel Vetter: > > On Thu, Jul 29, 2021 at 10:38 AM Christian König > > wrote: > >> Am 29.07.21 um 09:23 schrieb Daniel Vetter: > >>> On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: > As w

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Christian König
Am 29.07.21 um 13:59 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 12:21 PM Christian König wrote: Am 29.07.21 um 11:03 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 10:38 AM Christian König wrote: Am 29.07.21 um 09:23 schrieb Daniel Vetter: On Thu, Jul 29, 2021 at 09:03:30AM +0200, Chris

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread Daniel Vetter
On Thu, Jul 29, 2021 at 2:25 PM Christian König wrote: > > Am 29.07.21 um 13:59 schrieb Daniel Vetter: > > On Thu, Jul 29, 2021 at 12:21 PM Christian König > > wrote: > >> Am 29.07.21 um 11:03 schrieb Daniel Vetter: > >>> On Thu, Jul 29, 2021 at 10:38 AM Christian König > >>> wrote: > Am 29

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-29 Thread John Stultz
On Thu, Jul 29, 2021 at 12:24 AM Daniel Vetter wrote: > > On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: > > As we now knew controlling dma_fence synchronization from userspace is > > extremely dangerous and can not only deadlock drivers but trivially also the > > whole kernel me

Re: [PATCH 3/3] dma-buf: nuke SW_SYNC debugfs files

2021-07-30 Thread Hridya Valsaraju
On Thu, Jul 29, 2021 at 9:52 PM John Stultz wrote: > > On Thu, Jul 29, 2021 at 12:24 AM Daniel Vetter wrote: > > > > On Thu, Jul 29, 2021 at 09:03:30AM +0200, Christian König wrote: > > > As we now knew controlling dma_fence synchronization from userspace is > > > extremely dangerous and can not