Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 2017-08-17 at 15:38 +0200, Jiri Kosina wrote: > Hi, > > anything new on this front please? > > The splat (and therefore deadlock potential) is still there with current > Linus' tree. Sorry, haven't had more time to spend on it. I'll do it this evening. But, just to clarify, the

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

Hi, anything new on this front please? The splat (and therefore deadlock potential) is still there with current Linus' tree. Thanks, -- Jiri Kosina SUSE Labs

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 3 Aug 2017, Jiri Kosina wrote: > > I see the workqueue allocation you mentioned. I'll try to move this > > allocation out of the mutex and see how it goes. > > I have been briefly looking into this as well -- it'll basically have to > be moved out of the trans_pcie->mutex context, but

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 3 Aug 2017, Coelho, Luciano wrote: > Okay, so as I understand it the problem has been there for a long time, > but the splat is only coming up now because of Thomas' patch that adds > the lockdep map[1], right? Yeah, sorry, forgot to mention that pre-49dfe2a67797 kernels wouldn't

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 2017-08-03 at 13:02 +0300, Kalle Valo wrote: > "Coelho, Luciano" writes: > > > On Thu, 2017-08-03 at 11:10 +0200, Jiri Kosina wrote: > > > On Mon, 31 Jul 2017, Jiri Kosina wrote: > > > > > > > Hi, > > > > > > > > booting current Linus' tree, I'm seeing lockdep

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

"Coelho, Luciano" writes: > On Thu, 2017-08-03 at 11:10 +0200, Jiri Kosina wrote: >> On Mon, 31 Jul 2017, Jiri Kosina wrote: >> >> > Hi, >> > >> > booting current Linus' tree, I'm seeing lockdep splat (see the end of this >> > mail). >> > >> > Apparently, there is