linux-kernel - Re: [PATCH v5] wifi: ath11k: Fix memory reuse logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3448c268-06e6-4d82-8f6c-ec635e624fe7@quicinc.com>
Date: Wed, 7 May 2025 10:12:30 +0800
From: Baochen Qiang <quic_bqiang@...cinc.com>
To: Jeff Johnson <jeff.johnson@....qualcomm.com>,
        Muhammad Usama Anjum
	<usama.anjum@...labora.com>,
        Jeff Johnson <jjohnson@...nel.org>
CC: <kernel@...labora.com>, <linux-wireless@...r.kernel.org>,
        <ath11k@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] wifi: ath11k: Fix memory reuse logic



On 5/6/2025 10:37 PM, Jeff Johnson wrote:
> On 5/6/2025 6:10 AM, Muhammad Usama Anjum wrote:
>> On 5/6/25 12:17 AM, Jeff Johnson wrote:
>>> v2 feedback was not incorporated:
>>> For starters, can we make the subject a bit more specific, i.e.
>>> Fix MHI target memory reuse logic
>>>
>>> But don't repost for this -- I'll make that change in ath/pending
>> I'd changed again on the request of another reviewer. Please feel free
>> to change as you like. I don't have any opinion on it.
>>
>>>
>>> However, does ath12k need the same fix?
>> Looking at ath12k, there is similar code structure in
>> ath12k_qmi_alloc_chunk(). By adding some logging, we can confirm if
>> ath12k requires the fix or not. As a lot of code is similar in both
>> drivers, ath12k may require the same fix.
>>
>> I don't have access to ath12k. So I cannot test on it.
> 
> Baochen, do you want to propagate the change to ath12k?

Yeah, I can test and fix if same issue is there.