Re: [PATCH] audit: track the owner of the command mutex ourselves

On Thu, Feb 22, 2018 at 3:40 AM, Richard Guy Briggs wrote: > On 2018-02-20 11:55, Paul Moore wrote: >> From: Paul Moore >> >> Evidently the __mutex_owner() function was never intended for use >> outside the core mutex code, so build a thing locking wrapper

Re: [PATCH] audit: track the owner of the command mutex ourselves

On 2018-02-20 11:55, Paul Moore wrote: > From: Paul Moore > > Evidently the __mutex_owner() function was never intended for use > outside the core mutex code, so build a thing locking wrapper around > the mutex code which allows us to track the mutex owner. > > One,

[PATCH] audit: track the owner of the command mutex ourselves

From: Paul Moore Evidently the __mutex_owner() function was never intended for use outside the core mutex code, so build a thing locking wrapper around the mutex code which allows us to track the mutex owner. One, arguably positive, side effect is that this allows us to