Re: [BACKPORT 4.14.y v2 2/6] locking/lockdep: Add debug_locks check in __lock_downgrade()

2019-09-10 Thread Baolin Wang
On Tue, 10 Sep 2019 at 22:32, Greg KH wrote: > > On Thu, Sep 05, 2019 at 11:07:14AM +0800, Baolin Wang wrote: > > From: Waiman Long > > > > [Upstream commit 513e1073d52e55b8024b4f238a48de7587c64ccf] > > > > Tetsuo Handa had reported he saw an incorrect "downgrading a read lock" > > warning right

Re: [BACKPORT 4.14.y v2 2/6] locking/lockdep: Add debug_locks check in __lock_downgrade()

2019-09-10 Thread Greg KH
On Thu, Sep 05, 2019 at 11:07:14AM +0800, Baolin Wang wrote: > From: Waiman Long > > [Upstream commit 513e1073d52e55b8024b4f238a48de7587c64ccf] > > Tetsuo Handa had reported he saw an incorrect "downgrading a read lock" > warning right after a previous lockdep warning. It is likely that the > pr

[BACKPORT 4.14.y v2 2/6] locking/lockdep: Add debug_locks check in __lock_downgrade()

2019-09-04 Thread Baolin Wang
From: Waiman Long [Upstream commit 513e1073d52e55b8024b4f238a48de7587c64ccf] Tetsuo Handa had reported he saw an incorrect "downgrading a read lock" warning right after a previous lockdep warning. It is likely that the previous warning turned off lock debugging causing the lockdep to have incons