From: Calvin Owens <jcalvinowens@gmail.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath9k-devel@lists.ath9k.org, netdev@vger.kernel.org,
jcalvinowens@gmail.com
Subject: Re: [PATCH] mac80211: Use RCU protection in ieee80211_get_tx_rates()
Date: Thu, 13 Jun 2013 10:27:35 -0500 [thread overview]
Message-ID: <20130613152735.GA1822@gmail.com> (raw)
In-Reply-To: <51B843C9.9090500@openwrt.org>
On Wednesday 06/12 at 11:47 +0200, Felix Fietkau wrote:
> On 2013-06-12 10:00 AM, Calvin Owens wrote:
> > Copying the rate table should be done in an RCU read-side critical
> > section.
> I think this approach is wrong. The sta entry is also under RCU
> protection (no locking for read access in that part of the code.
> In a normal driver tx path, no extra rcu_read_lock/rcu_read_unlock is
> needed. Only if the driver does some scheduling outside of the tx
> function (which ath9k does), this RCU warning appears.
>
> How about this change instead:
> ---
> --- a/drivers/net/wireless/ath/ath9k/xmit.c
> +++ b/drivers/net/wireless/ath/ath9k/xmit.c
> @@ -1570,6 +1570,8 @@ void ath_txq_schedule(struct ath_softc *
> txq->axq_ampdu_depth >= ATH_AGGR_MIN_QDEPTH)
> return;
>
> + rcu_read_lock();
> +
> ac = list_first_entry(&txq->axq_acq, struct ath_atx_ac, list);
> last_ac = list_entry(txq->axq_acq.prev, struct ath_atx_ac, list);
>
> @@ -1608,8 +1610,10 @@ void ath_txq_schedule(struct ath_softc *
>
> if (ac == last_ac ||
> txq->axq_ampdu_depth >= ATH_AGGR_MIN_QDEPTH)
> - return;
> + break;
> }
> +
> + rcu_read_unlock();
> }
>
> /***********/
>
Yep, that stops the RCU warning for me.
Tested-by: Calvin Owens <jcalvinowens@gmail.com>
prev parent reply other threads:[~2013-06-13 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130609225120.GA2789@gmail.com>
[not found] ` <20130610042959.GA1902@gmail.com>
[not found] ` <1370950926.8356.14.camel@jlt4.sipsolutions.net>
2013-06-11 17:13 ` [PATCH] mac80211: ath9k: Use RCU protection calling ieee80211_get_tx_rates Calvin Owens
2013-06-11 19:55 ` Johannes Berg
[not found] ` <1370980523.8356.70.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-06-12 6:37 ` Kalle Valo
2013-06-12 7:56 ` Calvin Owens
2013-06-12 8:00 ` [PATCH] mac80211: Use RCU protection in ieee80211_get_tx_rates() Calvin Owens
2013-06-12 9:47 ` Felix Fietkau
2013-06-13 15:27 ` Calvin Owens [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=20130613152735.GA1822@gmail.com \
--to=jcalvinowens@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
/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).