linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Miaoqing Pan <quic_miaoqing@quicinc.com>
Cc: Johan Hovold <johan+linaro@kernel.org>,
	Jeff Johnson <jjohnson@kernel.org>,
	Remi Pommarel <repk@triplefau.lt>,
	Baochen Qiang <quic_bqiang@quicinc.com>,
	linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 4/4] wifi: ath12k: fix dest ring-buffer corruption when ring is full
Date: Fri, 6 Jun 2025 11:37:15 +0200	[thread overview]
Message-ID: <aEK2y8mMSQtbsKq2@hovoldconsulting.com> (raw)
In-Reply-To: <aEKylLhbfLusD3Kq@hovoldconsulting.com>

On Fri, Jun 06, 2025 at 11:19:16AM +0200, Johan Hovold wrote:
> On Fri, Jun 06, 2025 at 03:27:04PM +0800, Miaoqing Pan wrote:
> > On 6/4/2025 10:45 PM, Johan Hovold wrote:
> > > Add the missing memory barriers to make sure that destination ring
> > > descriptors are read before updating the tail pointer (and passing
> > > ownership to the device) to avoid memory corruption on weakly ordered
> > > architectures like aarch64 when the ring is full.
> 
> > > @@ -2184,6 +2187,10 @@ void ath12k_hal_srng_access_end(struct ath12k_base *ab, struct hal_srng *srng)
> > >   					   srng->u.src_ring.hp);
> > >   		} else {
> > >   			srng->u.dst_ring.last_hp = *srng->u.dst_ring.hp_addr;
> > > +			/* Make sure descriptor is read before updating the
> > > +			 * tail pointer.
> > > +			 */
> > > +			mb();
> > 
> > Is rmb() sufficient, since MMIO write already includes wmb()?
> 
> No, rmb() only orders reads against later reads.
> 
> [ The wmb() itself orders reads against later writes on aarch64, but
> that's not generally guaranteed and hence should not be relied on in
> driver code. ]

Sorry, I meant to say: an rmb() would order reads against later writes
on aarch64 (but that's not generally guaranteed and hence should not be
relied on in driver code).

Johan

  reply	other threads:[~2025-06-06  9:37 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
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 [this message]
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=aEK2y8mMSQtbsKq2@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=quic_bqiang@quicinc.com \
    --cc=quic_miaoqing@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;
as well as URLs for NNTP newsgroup(s).