From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jiale Yao <yaojiale02@163.com>,
Jeff Johnson <jjohnson@kernel.org>,
Shashidhar Lakkavalli <slakkavalli@datto.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-kernel@vger.kernel.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org
Subject: Re: [PATCH v2 0/5] wifi: ath: avoid IDR mutation while iterating
Date: Sat, 10 Oct 2026 10:07:26 -0700 [thread overview]
Message-ID: <d7f5ae97-05f0-487d-a31a-38c14e9c9e12@oss.qualcomm.com> (raw)
In-Reply-To: <20261003092104.520135-1-yaojiale02@163.com>
On 10/3/2026 2:20 AM, Jiale Yao wrote:
> The ath10k, ath11k, and ath12k cleanup paths walk an IDR while removing
> the current entry. idr_for_each() retains radix-tree iterator state across
> the callback, so that removal can invalidate the walk.
>
> Use idr_for_each_entry() in each cleanup path. It performs a fresh
> idr_get_next() lookup for every iteration, allowing the current entry to
> be removed safely before its skb is released. Keeping the existing locked
> removal helpers also ensures that a concurrent TX completion cannot find
> an IDR entry which points to an already freed skb.
>
> Changes in v2:
> - Rework the ath11k and ath12k pending management TX cleanup patches to
> remove each IDR entry before freeing its skb, as pointed out by
> Rameshkumar and Jeff.
> - Use idr_for_each_entry() for the pending cleanup callers instead of
> leaving freed skb pointers in the IDR until idr_destroy().
>
> Jiale Yao (5):
> wifi: ath10k: avoid IDR mutation during TX cleanup
> wifi: ath11k: avoid IDR mutation during pending mgmt TX cleanup
> wifi: ath11k: avoid IDR mutation during vif mgmt TX cleanup
> wifi: ath12k: avoid IDR mutation during pending mgmt TX cleanup
> wifi: ath12k: avoid IDR mutation during vif mgmt TX cleanup
>
> drivers/net/wireless/ath/ath10k/htt_tx.c | 7 ++++-
> drivers/net/wireless/ath/ath11k/core.c | 3 +--
> drivers/net/wireless/ath/ath11k/mac.c | 33 ++++++++++++------------
> drivers/net/wireless/ath/ath11k/mac.h | 2 +-
> drivers/net/wireless/ath/ath12k/core.c | 3 +--
> drivers/net/wireless/ath/ath12k/mac.c | 33 ++++++++++++------------
> drivers/net/wireless/ath/ath12k/mac.h | 2 +-
> 7 files changed, 44 insertions(+), 39 deletions(-)
>
(dropped obsolete codeaurora and quicinc addresses)
Version with the ath10k change updated is in my 'pending' branch:
https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/commit/?h=pending&id=3d806fd957b02ca1fa7991ffaf6c02ddd3dcbfe4
prev parent reply other threads:[~2026-10-10 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 9:20 Jiale Yao
2026-10-03 9:20 ` [PATCH v2 1/5] wifi: ath10k: avoid IDR mutation during TX cleanup Jiale Yao
2026-10-10 1:31 ` Jeff Johnson
2026-10-10 14:20 ` Jeff Johnson
2026-10-03 9:20 ` [PATCH v2 2/5] wifi: ath11k: avoid IDR mutation during pending mgmt " Jiale Yao
2026-10-03 9:21 ` [PATCH v2 3/5] wifi: ath11k: avoid IDR mutation during vif " Jiale Yao
2026-10-03 9:21 ` [PATCH v2 4/5] wifi: ath12k: avoid IDR mutation during pending " Jiale Yao
2026-10-03 9:21 ` [PATCH v2 5/5] wifi: ath12k: avoid IDR mutation during vif " Jiale Yao
2026-10-10 17:07 ` Jeff Johnson [this message]
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=d7f5ae97-05f0-487d-a31a-38c14e9c9e12@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=slakkavalli@datto.com \
--cc=yaojiale02@163.com \
/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®