linux-kernel - Re: [PATCH v2 0/9] Updated fence patch series

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: <20140702053758.GA7578@kroah.com>
Date:	Tue, 1 Jul 2014 22:37:58 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Cc:	linux-arch@...r.kernel.org, thellstrom@...are.com,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	linaro-mm-sig@...ts.linaro.org, robdclark@...il.com,
	thierry.reding@...il.com, ccross@...gle.com, daniel@...ll.ch,
	sumit.semwal@...aro.org, linux-media@...r.kernel.org
Subject: Re: [PATCH v2 0/9] Updated fence patch series

On Tue, Jul 01, 2014 at 12:57:02PM +0200, Maarten Lankhorst wrote:
> So after some more hacking I've moved dma-buf to its own subdirectory,
> drivers/dma-buf and applied the fence patches to its new place. I believe that the
> first patch should be applied regardless, and the rest should be ready now.
> :-)
> 
> Changes to the fence api:
> - release_fence -> fence_release etc.
> - __fence_init -> fence_init
> - __fence_signal -> fence_signal_locked
> - __fence_is_signaled -> fence_is_signaled_locked
> - Changing BUG_ON to WARN_ON in fence_later, and return NULL if it triggers.
> 
> Android can expose fences to userspace. It's possible to make the new fence
> mechanism expose the same fences to userspace by changing sync_fence_create
> to take a struct fence instead of a struct sync_pt. No other change is needed,
> because only the fence parts of struct sync_pt are used. But because the
> userspace fences are a separate problem and I haven't really looked at it yet
> I feel it should stay in staging, for now.

Ok, that's reasonable.

At first glance, this all looks "sane" to me, any objection from anyone
if I merge this through my driver-core tree for 3.17?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/