linux-kernel - Re: [PATCH] dma-fence: Correct return of dma_fence_driver

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5b828e1e-bebd-4730-8866-7a650c1f724f@igalia.com>
Date: Fri, 24 Oct 2025 17:06:04 +0100
From: Tvrtko Ursulin <tvrtko.ursulin@...lia.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: phasta@...nel.org, Sumit Semwal <sumit.semwal@...aro.org>,
 Gustavo Padovan <gustavo@...ovan.org>,
 Christian König <christian.koenig@....com>,
 linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dma-fence: Correct return of dma_fence_driver_name()


On 24/10/2025 15:36, Danilo Krummrich wrote:
> On 10/24/25 4:28 PM, Tvrtko Ursulin wrote:
>> On 24/10/2025 15:17, Danilo Krummrich wrote:
>>> On 10/24/25 3:37 PM, Tvrtko Ursulin wrote:
>>>> How about "unknown-driver", would that satisfy you?
>>>
>>> Honestly, the most accurate thing to say would be "fence-signaled", because
>>> that's the actual condition which causes the change.
>> Hm, ->get_driver_name() returning "fence-signaled" is not great, and debugfs
>> output in the form of "kernel fence: fence-signaled timeline-signaled seq 1234
>> signaled" feels a bit redundant. :shrug:
> 
> Indeed, what about "retired-driver"? Still implying that it's not just unknown,
> but that some process has finished. But without the ambiguity of "detached-driver".

Maybe "decoupled-driver"?

Regards,

Tvrtko