From: Johan Hovold <johan+linaro@kernel.org>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: Miaoqing Pan <quic_miaoqing@quicinc.com>,
Baochen Qiang <quic_bqiang@quicinc.com>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH v2 0/5] wifi: ath11k: fix dest ring-buffer corruption
Date: Wed, 4 Jun 2025 16:34:52 +0200 [thread overview]
Message-ID: <20250604143457.26032-1-johan+linaro@kernel.org> (raw)
As a follow up to commits:
6d037a372f81 ("wifi: ath11k: fix ring-buffer corruption")
ab52e3e44fe9 ("wifi: ath11k: fix rx completion meta data corruption")
add the remaining 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.
Also switch back to plain accesses for the descriptor fields which is
sufficient after the memory barrier.
New in v2 are two patches that adds the missing barriers also for source
rings and when updating the tail pointer for destination rings.
To avoid leaking ring details from the "hal" (lmac or non-lmac), the
barriers are added to the ath11k_hal_srng_access_end() helper. For
symmetry I therefore moved also the dest ring barriers into
ath11k_hal_srng_access_begin() and made the barrier conditional.
[ Due to this change I did not add Miaoqing's reviewed-by tag. ]
Johan
Changes in v2:
- add tested-on tags to plain access patches
- move destination barriers into begin helper
- fix source ring corruption (new patch)
- fix dest ring corruption when ring is full (new patch)
Johan Hovold (5):
wifi: ath11k: fix dest ring-buffer corruption
wifi: ath11k: use plain access for descriptor length
wifi: ath11k: use plain accesses for monitor descriptor
wifi: ath11k: fix source ring-buffer corruption
wifi: ath11k: fix dest ring-buffer corruption when ring is full
drivers/net/wireless/ath/ath11k/ce.c | 3 ---
drivers/net/wireless/ath/ath11k/dp_rx.c | 25 +++++++-----------
drivers/net/wireless/ath/ath11k/hal.c | 35 +++++++++++++++++++++----
3 files changed, 39 insertions(+), 24 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-04 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 14:34 Johan Hovold [this message]
2025-06-04 14:34 ` [PATCH v2 1/5] wifi: ath11k: fix dest ring-buffer corruption Johan Hovold
2025-06-05 9:12 ` Baochen Qiang
2025-06-25 9:59 ` Baochen Qiang
2025-06-04 14:34 ` [PATCH v2 2/5] wifi: ath11k: use plain access for descriptor length Johan Hovold
2025-06-25 9:59 ` Baochen Qiang
2025-06-04 14:34 ` [PATCH v2 3/5] wifi: ath11k: use plain accesses for monitor descriptor Johan Hovold
2025-06-25 9:59 ` Baochen Qiang
2025-06-04 14:34 ` [PATCH v2 4/5] wifi: ath11k: fix source ring-buffer corruption Johan Hovold
2025-06-25 10:00 ` Baochen Qiang
2025-06-04 14:34 ` [PATCH v2 5/5] wifi: ath11k: fix dest ring-buffer corruption when ring is full Johan Hovold
2025-06-25 10:00 ` Baochen Qiang
2025-06-26 23:15 ` [PATCH v2 0/5] wifi: ath11k: fix dest ring-buffer corruption Jeff Johnson
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=20250604143457.26032-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=quic_miaoqing@quicinc.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