From: Johan Hovold <johan@kernel.org>
To: Praneesh P <praneesh.p@oss.qualcomm.com>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
P Praneesh <quic_ppranees@quicinc.com>,
Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Miaoqing Pan <quic_miaoqing@quicinc.com>,
Remi Pommarel <repk@triplefau.lt>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] wifi: ath12k: fix dest ring-buffer corruption
Date: Tue, 17 Jun 2025 10:46:45 +0200 [thread overview]
Message-ID: <aFErdeZlT-Hm63pu@hovoldconsulting.com> (raw)
In-Reply-To: <63c2c889-0a09-4b25-a1d2-2aaa92d75d9f@oss.qualcomm.com>
On Mon, Jun 16, 2025 at 02:59:24PM +0530, Praneesh P wrote:
> On 6/5/2025 4:19 PM, Baochen Qiang wrote:
> > On 6/5/2025 6:00 PM, Johan Hovold wrote:
> >> On Thu, Jun 05, 2025 at 04:41:32PM +0800, Baochen Qiang wrote:
> >>> On 6/4/2025 10:45 PM, Johan Hovold wrote:
> >>>> Add the missing memory barrier to make sure that destination ring
> >>>> descriptors are read after the head pointers to avoid using stale data
> >>>> on weakly ordered architectures like aarch64.
> >>>>
> >>>> The barrier is added to the ath12k_hal_srng_access_begin() helper for
> >>>> symmetry with follow-on fixes for source ring buffer corruption which
> >>>> will add barriers to ath12k_hal_srng_access_end().
> >>>>
> >>>> Note that this may fix the empty descriptor issue recently worked around
> >>>> by commit 51ad34a47e9f ("wifi: ath12k: Add drop descriptor handling for
> >>>> monitor ring").
> >>> why? I would expect drunk cookies are valid in case of HAL_MON_DEST_INFO0_EMPTY_DESC,
> >>> rather than anything caused by reordering.
> >> Based on a quick look it seemed like this could possibly fall in the
> >> same category as some of the other workarounds I've spotted while
> >> looking into these ordering issues (e.g. f9fff67d2d7c ("wifi: ath11k:
> >> Fix SKB corruption in REO destination ring")).
> >>
> >> If you say this one is clearly unrelated, I'll drop the comment.
> > Praneesh, could you comment here since you made that change?
> Empty/Drop descriptor is intentionally issued by the hardware during
> backpressure scenario
> and is unrelated to the issue discussed in this patch series.
Thanks for confirming. I've dropped this comment in v3:
https://lore.kernel.org/lkml/20250617084402.14475-1-johan+linaro@kernel.org/
Johan
next prev parent reply other threads:[~2025-06-17 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 14:45 [PATCH v2 0/4] wifi: ath12k: fix dest ring-buffer corruption Johan Hovold
2025-06-04 14:45 ` [PATCH v2 1/4] " Johan Hovold
2025-06-05 8:41 ` Baochen Qiang
2025-06-05 10:00 ` Johan Hovold
2025-06-05 10:49 ` Baochen Qiang
2025-06-16 9:29 ` Praneesh P
2025-06-16 10:59 ` Baochen Qiang
2025-06-17 8:46 ` Johan Hovold [this message]
2025-06-04 14:45 ` [PATCH v2 2/4] wifi: ath12k: use plain access for descriptor length Johan Hovold
2025-06-04 14:45 ` [PATCH v2 3/4] wifi: ath12k: fix source ring-buffer corruption Johan Hovold
2025-06-04 14:45 ` [PATCH v2 4/4] wifi: ath12k: fix dest ring-buffer corruption when ring is full Johan Hovold
2025-06-06 7:27 ` Miaoqing Pan
2025-06-06 9:19 ` Johan Hovold
2025-06-06 9:37 ` Johan Hovold
2025-06-05 8:37 ` [PATCH v2 0/4] wifi: ath12k: fix dest ring-buffer corruption Baochen Qiang
2025-06-05 8:44 ` Johan Hovold
2025-06-05 8:51 ` Baochen Qiang
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=aFErdeZlT-Hm63pu@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ath12k@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=praneesh.p@oss.qualcomm.com \
--cc=quic_bqiang@quicinc.com \
--cc=quic_miaoqing@quicinc.com \
--cc=quic_ppranees@quicinc.com \
--cc=repk@triplefau.lt \
--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