From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Fernando Tapia" <fernan.tapia@fernandotapia.eu>,
<ath11k@lists.infradead.org>
Cc: <jjohnson@kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH ath-next] wifi: ath11k: don't create a duplicate peer on the same pdev
Date: Tue, 17 Nov 2026 09:51:32 +0100 [thread overview]
Message-ID: <DMXCW8192G9S.19BCMYODX8KSK@gmail.com> (raw)
In-Reply-To: <20261113120325.2913-1-fernan.tapia@fernandotapia.eu>
On Fri Nov 13, 2026 at 1:03 PM CET, Fernando Tapia wrote:
> ath11k_peer_create() accepts an address that is already a peer on
> another vdev, assuming the station is moving to another band. That holds
> when the old vdev is on another pdev. When both vdevs are on the same
> pdev, for example two AP interfaces on one 2.4 GHz radio, a station that
> moves between the two BSSes is authenticated on the new one while hostapd
> still has it on the old one. The WMI_PEER_CREATE for the second vdev then
> makes the IPQ8074 firmware (WLAN.HK.2.9.0.1-02146) assert:
>
> wal_peer_control.c:2904 Assertion is_graceful_to_handle failed
>
> followed by "failed to find peer ... after creation" on the host, and on
> AHB the whole SoC reboots. Tuya devices in pairing mode, which try both
> BSSes of a radio within a second, cause a reboot loop.
>
> Refuse the peer with -EBUSY while the address is still a peer on another
> vdev of the same pdev, without sending the command to the firmware. The
> station add fails as it already does after the assert, hostapd rejects
> that authentication, and the client succeeds on a retry once its old
> station is removed.
>
> Tested on a Xiaomi AX3600 (OpenWrt 25.12.5, kernel 6.12.94 with ath11k
> backported from 6.18.26) for 8 days. A smart plug moved between the two
> SSIDs of the 2.4 GHz radio in both directions, the sequence that had
> rebooted the router 8 times before: the new warning appears, the client
> connects on the retry about 4 s later, no firmware assert, no reboot.
>
> Assisted-by: LLM
> Signed-off-by: John Macias <dencity7@gmail.com>
> ---
Guys, I'm all for fixing bugs, but at some point you need to start reading
and searching the mailing list before pointing your LLM to any crashing
target. This is the third time someone posted a fix for this issue:
https://lore.kernel.org/linux-wireless/1316ed692b84f1d956e4854d9e974569a3961795.1784792420.git.repk@triplefau.lt/
https://lore.kernel.org/linux-wireless/20261001164139.370144-1-patricktlawler@gmail.com/
next prev parent reply other threads:[~2026-11-17 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 12:03 [PATCH ath-next] wifi: ath11k: don't create a duplicate peer on the same pdev Fernando Tapia
2026-11-17 8:51 ` Nicolas Escande [this message]
2026-11-17 9:04 ` Nicolas Escande
-- strict thread matches above, loose matches on Subject: below --
2026-11-16 18:11 Ure, Christopher R.
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=DMXCW8192G9S.19BCMYODX8KSK@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=fernan.tapia@fernandotapia.eu \
--cc=jjohnson@kernel.org \
--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