From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Kang Yang <kang.yang@oss.qualcomm.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next 0/6] wifi: ath12k: fix monitor RX buffer lifecycle issues
Date: Thu, 24 Sep 2026 07:35:28 -0700 [thread overview]
Message-ID: <6de23f77-4090-4093-94d7-0f5482e4b495@oss.qualcomm.com> (raw)
In-Reply-To: <c55d15c7-cbdd-4301-95c1-650db2a8bc05@oss.qualcomm.com>
On 9/24/2026 12:48 AM, Kang Yang wrote:
>
>
> On 9/16/2026 2:03 PM, Kang Yang wrote:
>> This series fixes several monitor RX buffer management bugs in the
>> monitor destination path.
>>
>> The fixes address leaked skb buffers, stale monitor descriptor state,
>> object lifetime issues, and incorrect DMA unmap handling observed in
>> various error and corner cases.
>>
>> Kang Yang (6):
>> wifi: ath12k: fix skb leak on paddr mismatch in wifi7 mon RX pop
>> wifi: ath12k: free pending MSDUs on duplicate mon link descriptor
>> wifi: ath12k: fix stale tail_msdu pointer returned from mpdu_pop
>> wifi: ath12k: place dp_mon_mpdu on stack in mon dst reap loop
>> wifi: ath12k: fix skb leak on monitor PPDU ID wraparound
>> wifi: ath12k: avoid double DMA unmap of held monitor RX buffers
>>
>> drivers/net/wireless/ath/ath12k/dp.c | 9 +++----
>> drivers/net/wireless/ath/ath12k/dp_mon.c | 15 ++++++------
>> drivers/net/wireless/ath/ath12k/dp_mon.h | 2 +-
>> .../net/wireless/ath/ath12k/wifi7/dp_mon.c | 24 +++++++++----------
>> 4 files changed, 24 insertions(+), 26 deletions(-)
>>
>>
>> base-commit: c3bace8584ca707e34ba837f65c2e9d566af4c2c
>
>
>
> Hi,jeff, do you have any comments? 😀
If you check patchwork using the Message-id of the individual patches (not the
cover letter) you'll see the status is Under Review which means it is under
active review. For example:
https://patchwork.kernel.org/project/linux-wireless/patch/20260916060325.854-2-kang.yang@oss.qualcomm.com/
Patches transition to that state when they are placed in my pending branch.
For best results when using patchwork you'll need to create an account and log
in since anonymous access has been severely restricted due to abuse by LLM
scraping robots.
/jeff
next prev parent reply other threads:[~2026-09-24 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 6:03 [PATCH ath-next 0/6] wifi: ath12k: fix monitor RX buffer lifecycle issues Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 1/6] wifi: ath12k: fix skb leak on paddr mismatch in wifi7 mon RX pop Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 2/6] wifi: ath12k: free pending MSDUs on duplicate mon link descriptor Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 3/6] wifi: ath12k: fix stale tail_msdu pointer returned from mpdu_pop Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 4/6] wifi: ath12k: place dp_mon_mpdu on stack in mon dst reap loop Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 5/6] wifi: ath12k: fix skb leak on monitor PPDU ID wraparound Kang Yang
2026-09-16 6:03 ` [PATCH ath-next 6/6] wifi: ath12k: avoid double DMA unmap of held monitor RX buffers Kang Yang
2026-09-17 10:44 ` [PATCH ath-next 0/6] wifi: ath12k: fix monitor RX buffer lifecycle issues Vasanthakumar Thiagarajan
2026-09-18 1:37 ` Baochen Qiang
2026-09-24 7:48 ` Kang Yang
2026-09-24 14:35 ` Jeff Johnson [this message]
2026-09-25 15:26 ` 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=6de23f77-4090-4093-94d7-0f5482e4b495@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=kang.yang@oss.qualcomm.com \
--cc=linux-wireless@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