On Wed, Mar 17, 2021 at 10:54:17PM -0400, Waiman Long wrote:
> On 3/17/21 10:24 PM, Boqun Feng wrote:
> > Hi Waiman,
> >
> > Just a question out of curiosity: how does this problem hide so long?
> > ;-) Because IIUC, both locktorture and ww_mutex_lock have been there for
> > a while, so why
On 3/17/21 10:24 PM, Boqun Feng wrote:
Hi Waiman,
Just a question out of curiosity: how does this problem hide so long?
;-) Because IIUC, both locktorture and ww_mutex_lock have been there for
a while, so why didn't we spot this earlier?
I ask just to make sure we don't introduce the problem
Hi Waiman,
Just a question out of curiosity: how does this problem hide so long?
;-) Because IIUC, both locktorture and ww_mutex_lock have been there for
a while, so why didn't we spot this earlier?
I ask just to make sure we don't introduce the problem because of some
subtle problems in
On Tue, 16 Mar 2021, Waiman Long wrote:
It was found that running the ww_mutex_lock-torture test produced the
following lockdep splat almost immediately:
[ 103.892638] ==
[ 103.892639] WARNING: possible circular locking dependency detected
It was found that running the ww_mutex_lock-torture test produced the
following lockdep splat almost immediately:
[ 103.892638] ==
[ 103.892639] WARNING: possible circular locking dependency detected
[ 103.892641] 5.12.0-rc3-debug+ #2
5 matches
Mail list logo