From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: "paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"Tobias Klausmann" <tobias.johannes.klausmann@mni.thm.de>,
lkml <linux-kernel@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"nbd@nbd.name" <nbd@nbd.name>
Subject: Re: regression: ath_tx_edma_tasklet() Illegal idle entry in RCU read-side critical section
Date: Tue, 20 Dec 2016 14:20:38 +0000 [thread overview]
Message-ID: <87oa06u1fu.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20b64afc-8270-27d5-6d45-592ce6dd24c7@gmail.com> (Gabriel C.'s message of "Mon, 19 Dec 2016 00:11:32 +0100")
Gabriel C <nix.or.die@gmail.com> writes:
> On 18.12.2016 21:14, Paul E. McKenney wrote:
>> On Sun, Dec 18, 2016 at 07:57:42PM +0000, Valo, Kalle wrote:
>>> Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> writes:
>>>
>>>> A patch for this is already floating on the ML for a while now latest:
>>>> (ath9k: do not return early to fix rcu unlocking)
>>>
>>> It's here:
>>>
>>> https://patchwork.kernel.org/patch/9472709/
>>
>> Feel free to add:
>>
>> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>>
>
> This patch fixes the bug for me.
>
> You can add my Tested-by if you wish.
>
> Tested-by: Gabriel Craciunescu <nix.or.die@gmail.com>
I added both of these to the commit log, thanks.
--
Kalle Valo
prev parent reply other threads:[~2016-12-20 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 13:52 regression: ath_tx_edma_tasklet() Illegal idle entry in RCU read-side critical section Gabriel C
2016-12-18 15:59 ` Paul E. McKenney
2016-12-18 16:17 ` Tobias Klausmann
2016-12-18 19:57 ` Valo, Kalle
2016-12-18 20:04 ` Tobias Klausmann
2016-12-18 20:14 ` Paul E. McKenney
2016-12-18 23:11 ` Gabriel C
2016-12-20 14:20 ` Valo, Kalle [this message]
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=87oa06u1fu.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tobias.johannes.klausmann@mni.thm.de \
/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