linux-kernel - [PATCH 0/3] dma-buf: Check status of enable-signaling bit on debug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220927172409.484061-1-Arvind.Yadav@amd.com>
Date:   Tue, 27 Sep 2022 22:54:06 +0530
From:   Arvind Yadav <Arvind.Yadav@....com>
To:     <Christian.Koenig@....com>, <andrey.grodzovsky@....com>,
        <shashank.sharma@....com>, <amaranath.somalapuram@....com>,
        <Arunpravin.PaneerSelvam@....com>, <sumit.semwal@...aro.org>,
        <gustavo@...ovan.org>, <airlied@...ux.ie>, <daniel@...ll.ch>,
        <linux-media@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
        <linaro-mm-sig@...ts.linaro.org>, <linux-kernel@...r.kernel.org>
CC:     Arvind Yadav <Arvind.Yadav@....com>
Subject: [PATCH 0/3] dma-buf: Check status of enable-signaling bit on debug

Fence signaling must be enabled to make sure that
the dma_fence_is_signaled() and dma_fence_is_signaled_locked()
function ever returns true. Since drivers and implementations
sometimes mess this up, this ensures correct behaviour when
DEBUG_WW_MUTEX_SLOWPATH is used during debugging.
This should make any implementation bugs resulting in not
signaled fences much more obvious.


Arvind Yadav (3):
  [PATCH 1/3] dma-buf: Remove the signaled bit status check
  [PATCH 2/3] dma-buf: Enable signaling on fence for sw_sync
  [PATCH 3/3] dma-buf: Check status of enable-signaling bit on debug

 drivers/dma-buf/dma-fence.c | 5 -----
 drivers/dma-buf/sw_sync.c   | 2 ++
 include/linux/dma-fence.h   | 5 +++++
 3 files changed, 7 insertions(+), 5 deletions(-)

-- 
2.25.1