Hi Christian, On Thu, 20 Nov 2025 at 20:30, Christian König <[email protected]> wrote: > > The SW-sync functionality should only be used for testing and debugging > since it is inherently unsave.
Thank you for this patch, LGTM. Please feel free to add: Acked-by: Sumit Semwal <[email protected]> Best, Sumit. > > Signed-off-by: Christian König <[email protected]> > --- > drivers/dma-buf/sw_sync.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c > index 3c20f1d31cf5..6f09d13be6b6 100644 > --- a/drivers/dma-buf/sw_sync.c > +++ b/drivers/dma-buf/sw_sync.c > @@ -8,6 +8,7 @@ > #include <linux/file.h> > #include <linux/fs.h> > #include <linux/uaccess.h> > +#include <linux/panic.h> > #include <linux/slab.h> > #include <linux/sync_file.h> > > @@ -349,6 +350,9 @@ static long sw_sync_ioctl_create_fence(struct > sync_timeline *obj, > struct sync_file *sync_file; > struct sw_sync_create_fence_data data; > > + /* SW sync fence are inherently unsafe and can deadlock the kernel */ > + add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK); > + > if (fd < 0) > return fd; > > -- > 2.43.0 >
