From: Johan Hovold <johan@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Miaoqing Pan <quic_miaoqing@quicinc.com>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/3] wifi: ath11k: fix dest ring-buffer corruption
Date: Wed, 25 Jun 2025 11:34:10 +0200 [thread overview]
Message-ID: <aFvCkiJCRmwtqhWt@hovoldconsulting.com> (raw)
In-Reply-To: <70b25ff3-b366-4e2d-a52a-0b2d50ce88c4@quicinc.com>
On Wed, Jun 25, 2025 at 10:06:21AM +0800, Baochen Qiang wrote:
> On 5/26/2025 7:48 PM, Johan Hovold wrote:
> > Add the missing memory barriers to make sure that destination ring
> > descriptors are read after the head pointers to avoid using stale data
> > on weakly ordered architectures like aarch64.
> >
> > Tested-on: WCN6855 hw2.1 WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
> >
> > Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
> > Cc: stable@vger.kernel.org # 5.6
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > diff --git a/drivers/net/wireless/ath/ath11k/dp_tx.c b/drivers/net/wireless/ath/ath11k/dp_tx.c
> > index 8522c67baabf..549d17d90503 100644
> > --- a/drivers/net/wireless/ath/ath11k/dp_tx.c
> > +++ b/drivers/net/wireless/ath/ath11k/dp_tx.c
> > @@ -700,6 +700,9 @@ void ath11k_dp_tx_completion_handler(struct ath11k_base *ab, int ring_id)
> >
> > ath11k_hal_srng_access_begin(ab, status_ring);
> >
> > + /* Make sure descriptor is read after the head pointer. */
> > + dma_rmb();
> > +
> > while ((ATH11K_TX_COMPL_NEXT(tx_ring->tx_status_head) !=
> > tx_ring->tx_status_tail) &&
> > (desc = ath11k_hal_srng_dst_get_next_entry(ab, status_ring))) {
>
> Johan, dma_rmb() is put inside _srng_access_begin() for ath12k, but here inside each
> caller. Can we achieve consistency between two drivers?
I moved into into the helper also for ath11k in v2:
https://lore.kernel.org/lkml/20250604143457.26032-2-johan+linaro@kernel.org/
Johan
next prev parent reply other threads:[~2025-06-25 9:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:48 [PATCH 0/3] wifi: ath11k: fix dest ring-buffer corruption Johan Hovold
2025-05-26 11:48 ` [PATCH 1/3] " Johan Hovold
2025-05-29 7:03 ` Miaoqing Pan
2025-06-02 8:03 ` Johan Hovold
2025-06-03 10:52 ` Baochen Qiang
2025-06-03 11:51 ` Johan Hovold
2025-06-04 2:16 ` Baochen Qiang
2025-06-04 6:59 ` Johan Hovold
2025-06-05 8:16 ` Baochen Qiang
2025-06-04 2:34 ` Miaoqing Pan
2025-06-04 5:32 ` Miaoqing Pan
2025-06-04 7:06 ` Johan Hovold
2025-06-04 7:57 ` Miaoqing Pan
2025-06-04 8:07 ` Johan Hovold
2025-06-04 8:18 ` Miaoqing Pan
2025-06-04 16:24 ` Jeff Johnson
2025-06-05 4:01 ` Miaoqing Pan
2025-06-05 10:17 ` Johan Hovold
2025-06-05 10:54 ` Baochen Qiang
2025-06-06 0:52 ` Miaoqing Pan
2025-06-06 2:02 ` Baochen Qiang
2025-06-06 7:43 ` Miaoqing Pan
2025-06-25 2:06 ` Baochen Qiang
2025-06-25 9:34 ` Johan Hovold [this message]
2025-05-26 11:48 ` [PATCH 2/3] wifi: ath11k: use plain access for descriptor length Johan Hovold
2025-05-26 11:48 ` [PATCH 3/3] wifi: ath11k: use plain accesses for monitor descriptor Johan Hovold
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=aFvCkiJCRmwtqhWt@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=quic_miaoqing@quicinc.com \
--cc=stable@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