Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

2018-02-20 Thread kbuild test robot
Hi Christian, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180220] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/comm

Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

2018-02-20 Thread kbuild test robot
Hi Christian, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180220] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/comm

Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

2018-02-20 Thread Daniel Vetter
On Tue, Feb 20, 2018 at 03:49:46PM +0100, Christian König wrote: > amdgpu needs to verify if userspace sends us valid addresses and the simplest > way of doing this is to check if the buffer object is locked with the ticket > of the current submission. > > Clean up the access to the ww_mutex inter

Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

2018-02-20 Thread Eric Engestrom
On Tuesday, 2018-02-20 15:49:46 +0100, Christian König wrote: > amdgpu needs to verify if userspace sends us valid addresses and the simplest > way of doing this is to check if the buffer object is locked with the ticket > of the current submission. > > Clean up the access to the ww_mutex internal

[PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

2018-02-20 Thread Christian König
amdgpu needs to verify if userspace sends us valid addresses and the simplest way of doing this is to check if the buffer object is locked with the ticket of the current submission. Clean up the access to the ww_mutex internals by providing a function for this and extend the check to the thread ow