e 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
>>>>>&
o the lock downgrade warning.
Fix that by add a check for debug_locks at the beginning of
__lock_downgrade().
Please drop "[PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in
__lock_downgrade()".
We had a revert patch shown below in the past.
We had a revert in the stable trees,
t by add a check for debug_locks at the beginning of
> > __lock_downgrade().
>
> Please drop "[PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in
> __lock_downgrade()".
> We had a revert patch shown below in the past.
Ugh, I missed that, thanks.
> "[PATCH 4.19
d off lock debugging causing the lockdep to have
>>>> inconsistency states leading to the lock downgrade warning.
>>>>
>>>> Fix that by add a check for debug_locks at the beginning of
>>>> __lock_downgrade().
>>> Please drop "[PATCH 4.19 36/63]
check for debug_locks at the beginning of
__lock_downgrade().
Please drop "[PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in
__lock_downgrade()".
We had a revert patch shown below in the past.
We had a revert in the stable trees, but that revert was incorrect.
T
ading to the lock downgrade warning.
>>>
>>> Fix that by add a check for debug_locks at the beginning of
>>> __lock_downgrade().
>>
>> Please drop "[PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in
>> __lock_downgrade()".
>
a previous lockdep warning. It is likely that the
previous warning turned off lock debugging causing the lockdep to have
inconsistency states leading to the lock downgrade warning.
Fix that by add a check for debug_locks at the beginning of
__lock_downgrade().
Please drop "[PATCH 4.19 36/63]
s likely that the
> previous warning turned off lock debugging causing the lockdep to have
> inconsistency states leading to the lock downgrade warning.
>
> Fix that by add a check for debug_locks at the beginning of
> __lock_downgrade().
Please drop "[PATCH 4.19 36/63] locking/loc
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
inco
9 matches
Mail list logo
