From: Christian König Date: Tue, 10 Dec 2024 09:08:42 +0000 (+0100) Subject: dma-buf: fix incorrect dma-fence documentation v2 X-Git-Tag: v6.16-rc1~144^2~21^2~266 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2b2d7ca7ce25fbec8389e7d85e57742caa47c97d;p=thirdparty%2Flinux.git dma-buf: fix incorrect dma-fence documentation v2 There isn't much worse than documentation giving an incorrect advise. Grabbing a spinlock while interrupts are disabled usually means that you must also disable interrupts for all other uses of this spinlock. Otherwise really hard to debug issues can occur. So fix that invalid documentation. v2: use Dmitry's suggestion on the documentation Signed-off-by: Christian König Reviewed-by: Simona Vetter (v1) Link: https://patchwork.freedesktop.org/patch/msgid/20250211163109.12200-2-christian.koenig@amd.com --- diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h index e7ad819962e3e..52587d390acab 100644 --- a/include/linux/dma-fence.h +++ b/include/linux/dma-fence.h @@ -169,8 +169,8 @@ struct dma_fence_ops { * implementation know that there is another driver waiting on the * signal (ie. hw->sw case). * - * This function can be called from atomic context, but not - * from irq context, so normal spinlocks can be used. + * This is called with irq's disabled, so only spinlocks which disable + * IRQ's can be used in the code outside of this callback. * * A return value of false indicates the fence already passed, * or some failure occurred that made it impossible to enable