linux-kernel - Re: [PATCH 02/11] dma-buf/fence: add fence

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]

Date:	Wed, 1 Jun 2016 11:01:08 -0300
From:	Gustavo Padovan <gustavo@...ovan.org>
To:	Christian König <deathsimple@...afone.de>
Cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	daniel@...ll.ch, chris@...is-wilson.co.uk
Subject: Re: [PATCH 02/11] dma-buf/fence: add fence_array fences v6

Hi Christian,

2016-06-01 Christian König <deathsimple@...afone.de>:

> From: Gustavo Padovan <gustavo.padovan@...labora.co.uk>
> 
> struct fence_collection inherits from struct fence and carries a
> collection of fences that needs to be waited together.
> 
> It is useful to translate a sync_file to a fence to remove the complexity
> of dealing with sync_files on DRM drivers. So even if there are many
> fences in the sync_file that needs to waited for a commit to happen,
> they all get added to the fence_collection and passed for DRM use as
> a standard struct fence.
> 
> That means that no changes needed to any driver besides supporting fences.
> 
> fence_collection's fence doesn't belong to any timeline context, so
> fence_is_later() and fence_later() are not meant to be called with
> fence_collections fences.

The commit message needs to be fixed to say mention fence_array instead
of fence_collection and we do create fence contexts for fence_arrays
now.

	Gustavo