From: Johan Hovold <johan@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Miaoqing Pan <quic_miaoqing@quicinc.com>,
Steev Klimaszewski <steev@kali.org>,
Clayton Craft <clayton@craftyguy.net>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
ath11k@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: fix rx completion meta data corruption
Date: Mon, 24 Mar 2025 16:06:58 +0100 [thread overview]
Message-ID: <Z-F1EoFxY3qVZiXZ@hovoldconsulting.com> (raw)
In-Reply-To: <5d872cf0-ca57-4017-b06e-fce9c11813dc@oss.qualcomm.com>
On Mon, Mar 24, 2025 at 08:03:15AM -0700, Jeff Johnson wrote:
> On 3/21/2025 7:53 AM, Johan Hovold wrote:
> > Add the missing memory barrier to make sure that the REO dest ring
> > descriptor is read after the head pointer to avoid using stale data on
> > weakly ordered architectures like aarch64.
> >
> > This may fix the ring-buffer corruption worked around by commit
> > f9fff67d2d7c ("wifi: ath11k: Fix SKB corruption in REO destination
> > ring") by silently discarding data, and may possibly also address user
> > reported errors like:
> >
> > ath11k_pci 0006:01:00.0: msdu_done bit in attention is not set
> >
> > 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
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=218005
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
>
> Does this supersede:
> [PATCH] wifi: ath11k: fix ring-buffer corruption
No, this is a separate fix. There are more places where barriers are
missing, I'll try send some further fixes during the week as well.
Johan
next prev parent reply other threads:[~2025-03-24 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 14:53 [PATCH] wifi: ath11k: fix rx completion meta data corruption Johan Hovold
2025-03-22 20:32 ` Steev Klimaszewski
2025-03-24 7:52 ` Johan Hovold
2025-03-24 6:15 ` Clayton Craft
2025-03-24 7:49 ` Johan Hovold
2025-03-24 15:03 ` Jeff Johnson
2025-03-24 15:06 ` Johan Hovold [this message]
2025-05-16 18:34 ` 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=Z-F1EoFxY3qVZiXZ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=clayton@craftyguy.net \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=jjohnson@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_miaoqing@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=steev@kali.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