From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: ath9k-devel@qca.qualcomm.com, kvalo@codeaurora.org, davem@davemloft.net
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: [PATCH] ath9k: Fix possible data races in ath_set_channel()
Date: Sun, 12 Jan 2020 01:15:28 +0800 [thread overview]
Message-ID: <20200111171528.7053-1-baijiaju1990@gmail.com> (raw)
The functions ath9k_config() and ath_ani_calibrate() may be concurrently
executed.
A variable survey->filled is accessed with holding a spinlock
common->cc_lock, through:
ath_ani_calibrate()
spin_lock_irqsave(&common->cc_lock, flags);
ath_update_survey_stats()
ath_update_survey_nf()
survey->filled |= SURVEY_INFO_NOISE_DBM;
The identical variables sc->cur_survey->filled and
sc->survey[pos].filled is accessed without holding this lock, through:
ath9k_config()
ath_chanctx_set_channel()
ath_set_channel()
sc->cur_survey->filled &= ~SURVEY_INFO_IN_USE;
sc->cur_survey->filled |= SURVEY_INFO_IN_USE;
else if (!(sc->survey[pos].filled & SURVEY_INFO_IN_USE))
ath_update_survey_nf
survey->filled |= SURVEY_INFO_NOISE_DBM;
Thus, possible data races may occur.
To fix these data races, in ath_set_channel(), these variables are
accessed with holding the spinlock common->cc_lock.
These data races are found by the runtime testing of our tool DILP-2.
Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
---
drivers/net/wireless/ath/ath9k/channel.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath9k/channel.c b/drivers/net/wireless/ath/ath9k/channel.c
index fd61ae4782b6..b16f7f65e9c6 100644
--- a/drivers/net/wireless/ath/ath9k/channel.c
+++ b/drivers/net/wireless/ath/ath9k/channel.c
@@ -54,6 +54,7 @@ static int ath_set_channel(struct ath_softc *sc)
* Reset the survey data for the new channel, unless we're switching
* back to the operating channel from an off-channel operation.
*/
+ spin_lock_irqsave(&common->cc_lock, flags);
if (!sc->cur_chan->offchannel && sc->cur_survey != &sc->survey[pos]) {
if (sc->cur_survey)
sc->cur_survey->filled &= ~SURVEY_INFO_IN_USE;
@@ -65,6 +66,7 @@ static int ath_set_channel(struct ath_softc *sc)
} else if (!(sc->survey[pos].filled & SURVEY_INFO_IN_USE)) {
memset(&sc->survey[pos], 0, sizeof(struct survey_info));
}
+ spin_unlock_irqrestore(&common->cc_lock, flags);
hchan = &sc->sc_ah->channels[pos];
r = ath_reset(sc, hchan);
@@ -75,8 +77,11 @@ static int ath_set_channel(struct ath_softc *sc)
* channel is only available after the hardware reset. Copy it to
* the survey stats now.
*/
- if (old_pos >= 0)
+ if (old_pos >= 0) {
+ spin_lock_irqsave(&common->cc_lock, flags);
ath_update_survey_nf(sc, old_pos);
+ spin_unlock_irqrestore(&common->cc_lock, flags);
+ }
/* Enable radar pulse detection if on a DFS channel. Spectral
* scanning and radar detection can not be used concurrently.
--
2.17.1
next reply other threads:[~2020-01-11 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 17:15 Jia-Ju Bai [this message]
2020-01-13 7:17 ` Kalle Valo
2020-01-13 8:27 ` Felix Fietkau
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=20200111171528.7053-1-baijiaju1990@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
all inboxes | Powered by JetHome®