From: Bruno Randolf <br1@einfach.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linville@tuxdriver.com, jirislaby@gmail.com, mickflemm@gmail.com,
lrodriguez@atheros.com, linux-wireless@vger.kernel.org,
ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH 3/4] ath5k: fix race condition in tx desc processing
Date: Thu, 8 Apr 2010 13:15:36 +0900 [thread overview]
Message-ID: <201004081315.36390.br1@einfach.org> (raw)
In-Reply-To: <1270698959-7844-4-git-send-email-me@bobcopeland.com>
On Thursday 08 April 2010 12:55:58 Bob Copeland wrote:
> As pointed out by Benoit Papillault, there is a potential
> race condition between the host and the hardware in reading
> the next link in the transmit descriptor list:
>
> cpu0 hw
> tx for buf completed
> raise tx_ok interrupt
> process buf
> buf->ds_link = 0
> read buf->ds_link
>
> This change checks txdp before processing a descriptor
> (if there are any subsequent descriptors) to see if
> hardware moved on. We'll then process this descriptor on
> the next tasklet.
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> ---
> drivers/net/wireless/ath/ath5k/base.c | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath5k/base.c
> b/drivers/net/wireless/ath/ath5k/base.c index 1e10439..f90c679 100644
> --- a/drivers/net/wireless/ath/ath5k/base.c
> +++ b/drivers/net/wireless/ath/ath5k/base.c
> @@ -2080,6 +2080,17 @@ ath5k_tx_processq(struct ath5k_softc *sc, struct
> ath5k_txq *txq) list_for_each_entry_safe(bf, bf0, &txq->q, list) {
> ds = bf->desc;
>
> + /*
> + * It's possible that the hardware can say the buffer is
> + * completed when it hasn't yet loaded the ds_link from
> + * host memory and moved on. If there are more TX
> + * descriptors in the queue, wait for TXDP to change
> + * before processing this one.
> + */
> + if (ath5k_hw_get_txdp(sc->ah, txq->qnum) == bf->daddr &&
> + !list_is_last(&bf->list, &txq->q))
> + break;
> +
> ret = sc->ah->ah_proc_tx_desc(sc->ah, ds, &ts);
> if (unlikely(ret == -EINPROGRESS))
> break;
for whatever it's worth :-)
Acked-by: Bruno Randolf <br1@einfach.org>
next prev parent reply other threads:[~2010-04-08 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 3:55 [PATCH 0/4] ath5k: misc fixes Bob Copeland
2010-04-08 3:55 ` [PATCH 1/4] ath5k: correct channel setting for 2.5 mhz spacing Bob Copeland
2010-04-08 4:14 ` Bruno Randolf
2010-04-08 3:55 ` [PATCH 2/4] ath5k: clean up queue manipulation Bob Copeland
2010-04-08 4:15 ` Bruno Randolf
2010-04-08 3:55 ` [PATCH 3/4] ath5k: fix race condition in tx desc processing Bob Copeland
2010-04-08 4:15 ` Bruno Randolf [this message]
2010-04-08 3:55 ` [PATCH 4/4] ath5k: add bounds check to pdadc table Bob Copeland
2010-04-08 4:15 ` Bruno Randolf
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=201004081315.36390.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.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).