Re: [PATCH -tip] locking/rwsem: Check for operations on an uninitialized rwsem

2019-07-29 Thread Waiman Long
On 7/29/19 12:47 AM, Davidlohr Bueso wrote: > Currently rwsems is the only locking primitive that lacks this > debug feature. Add it under CONFIG_DEBUG_RWSEMS and do the magic > checking in the locking fastpath (trylock) operation such that > we cover all cases. The unlocking part is pretty straigh

Re: [PATCH -tip] locking/rwsem: Check for operations on an uninitialized rwsem

2019-07-29 Thread Peter Zijlstra
On Sun, Jul 28, 2019 at 09:47:35PM -0700, Davidlohr Bueso wrote: > Currently rwsems is the only locking primitive that lacks this > debug feature. Add it under CONFIG_DEBUG_RWSEMS and do the magic > checking in the locking fastpath (trylock) operation such that > we cover all cases. The unlocking p

[PATCH -tip] locking/rwsem: Check for operations on an uninitialized rwsem

2019-07-28 Thread Davidlohr Bueso
Currently rwsems is the only locking primitive that lacks this debug feature. Add it under CONFIG_DEBUG_RWSEMS and do the magic checking in the locking fastpath (trylock) operation such that we cover all cases. The unlocking part is pretty straightforward. Signed-off-by: Davidlohr Bueso --- incl