From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: Jiri Kosina <jikos@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxwifi@intel.com, rui.zhang@intel.com, edubezval@gmail.com,
linux-pm@vger.kernel.org, david.weinehall@intel.com,
johannes.berg@intel.com, sara.sharon@intel.com,
emmanuel.grumbach@intel.com
Subject: Re: [PATCH v2] iwlwifi: pcie: move rx workqueue initialization to iwl_trans_pcie_alloc()
Date: Tue, 29 Aug 2017 11:19:04 +0300 [thread overview]
Message-ID: <87inh6vlaf.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1503604818.15969.433.camel@coelho.fi> (Luca Coelho's message of "Thu, 24 Aug 2017 23:00:18 +0300")
Luca Coelho <luca@coelho.fi> writes:
> On Thu, 2017-08-24 at 21:56 +0200, Jiri Kosina wrote:
>> On Thu, 24 Aug 2017, Luca Coelho wrote:
>>
>> > > Work queues cannot be allocated when a mutex is held because the mutex
>> > > may be in use and that would make it sleep. Doing so generates the
>> > > following splat with 4.13+:
>> > >
>> > > [ 19.513298] ======================================================
>> > > [ 19.513429] WARNING: possible circular locking dependency detected
>> > > [ 19.513557] 4.13.0-rc5+ #6 Not tainted
>> > > [ 19.513638] ------------------------------------------------------
>> > > [ 19.513767] cpuhp/0/12 is trying to acquire lock:
>> > > [ 19.513867] (&tz->lock){+.+.+.}, at: [<ffffffff924afebb>]
>> > > thermal_zone_get_temp+0x5b/0xb0
>> > > [ 19.514047]
>> > > [ 19.514047] but task is already holding lock:
>> > > [ 19.514166] (cpuhp_state){+.+.+.}, at: [<ffffffff91cc4baa>]
>> > > cpuhp_thread_fun+0x3a/0x210
>> > > [ 19.514338]
>> > > [ 19.514338] which lock already depends on the new lock.
>> > >
>> > > This lock dependency already existed with previous kernel versions,
>> > > but it was not detected until commit 49dfe2a67797 ("cpuhotplug: Link
>> > > lock stacks for hotplug callbacks") was introduced.
>> > >
>> > > Reported-by: David Weinehall <david.weinehall@intel.com>
>> > > Reported-by: Jiri Kosina <jikos@kernel.org>
>> > > Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
>> >
>> > Jiri, did you have a chance to try this out? I'm about to ask Kalle to
>> > merge this so it gets in in time for 4.13-rc7.
>>
>> Sorry, I am almost completely offline for one more week (vacation), and
>> will not have access to the affected system before that.
>
> Sounds good! Enjoy! ;)
>
>
>> But this indeed
>> looks like a correct fix to me, so feel free to add
>>
>> Acked-by: Jiri Kosina <jkosina@suse.cz>
>>
>> I'll be able to provide my Tested-by: eventually only in ~10 days.
>
>
> Kalle already picked it up in wireless-drivers and this should make it's
> way to 4.13-rc7 (we hope).
It (10a54d8196d1) didn't make it to -rc7 but it's in net tree now and
should make it to the next release on Sunday (either -rc8 or the final).
--
Kalle Valo
next prev parent reply other threads:[~2017-08-29 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LSU.2.20.1707311300440.4705@cbobk.fhfr.pm>
[not found] ` <alpine.LSU.2.20.1708031107230.30597@cbobk.fhfr.pm>
[not found] ` <1501753405.15969.43.camel@intel.com>
2017-08-03 10:02 ` [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock Kalle Valo
2017-08-03 11:28 ` Coelho, Luciano
2017-08-03 11:34 ` Jiri Kosina
2017-08-03 13:09 ` Jiri Kosina
2017-08-17 13:38 ` Jiri Kosina
2017-08-17 14:02 ` Coelho, Luciano
2017-08-22 7:32 ` [PATCH] iwlwifi: pcie: move rx workqueue initialization to iwl_trans_pcie_alloc() Luca Coelho
2017-08-22 7:37 ` [PATCH v2] " Luca Coelho
2017-08-24 6:00 ` Luca Coelho
2017-08-24 19:56 ` Jiri Kosina
2017-08-24 20:00 ` Luca Coelho
2017-08-29 8:19 ` Kalle Valo [this message]
2017-09-04 11:43 ` Jiri Kosina
2017-09-04 11:44 ` Luca Coelho
2017-08-24 13:50 ` [v2] " Kalle Valo
2017-08-30 14:57 ` [PATCH v2] " David Weinehall
2017-08-31 6:11 ` Luca Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inh6vlaf.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=david.weinehall@intel.com \
--cc=edubezval@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=jikos@kernel.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
--cc=rui.zhang@intel.com \
--cc=sara.sharon@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).