From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Johan Hovold <johan@kernel.org>,
Miaoqing Pan <quic_miaoqing@quicinc.com>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Johan Hovold <johan+linaro@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
<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: Thu, 5 Jun 2025 18:54:48 +0800 [thread overview]
Message-ID: <bc2afbd6-2876-4f36-81cf-ad8960588a02@quicinc.com> (raw)
In-Reply-To: <aEFupJ_nd9ryaTVt@hovoldconsulting.com>
On 6/5/2025 6:17 PM, Johan Hovold wrote:
> On Thu, Jun 05, 2025 at 12:01:29PM +0800, Miaoqing Pan wrote:
>> On 6/5/2025 12:24 AM, Jeff Johnson wrote:
>>> On 6/3/2025 7:34 PM, Miaoqing Pan wrote:
>>>> We previously had extensive discussions on this topic in the
>>>> https://lore.kernel.org/linux-wireless/ecfe850c-b263-4bee-b888-c34178e690fc@quicinc.com/
>>>> thread. On my platform, dma_rmb() did not work as expected. The issue
>>>> only disappeared after disabling PCIe endpoint relaxed ordering in
>>>> firmware side. So it seems that HP was updated (Memory write) before
>>>> descriptor (Memory write), which led to the problem.
>>>
>>> Have all ath11k and ath12k firmware been updated to prevent this problem from
>>> the firmware side?
>>>
>> No, as this is not a widespread issue, and addressing it would require
>> modifying the core underlying modules of the firmware. Therefore, we
>> chose not to proceed with that approach but instead used the workaround
>> patch I previously submitted.
If firmware has a concern, how about doing it in host? As I know it is only a register in
PCI config space?
>
> I strongly suggest you fix this at the firmware level rather than try to
> work around it in the kernel to avoid playing whack-a-mole whenever a
> new (hard to track down) bug shows up.
>
> The barriers should be enough, but if they are not then the firmware
> must be fixed.
>
> Johan
next prev parent reply other threads:[~2025-06-05 10:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:48 [PATCH 0/3] " 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 [this message]
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
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=bc2afbd6-2876-4f36-81cf-ad8960588a02@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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
all inboxes | Powered by JetHome®