From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Mehmet Fide" <mehmet.fide@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH wireless] wifi: mac80211: abort chanswitch when leaving an IBSS
Date: Tue, 27 Oct 2026 10:01:19 +0000 [thread overview]
Message-ID: <5c3f973b90b90271771f6deaa8748f8ece50b370@linux.dev> (raw)
In-Reply-To: <20261026152543.1272978-1-mehmet.fide@gmail.com>
October 26, 2026 at 4:25 PM, "Mehmet Fide" <mehmet.fide@gmail.com> wrote:
>
> Hi Luka,
>
> >
> > So if I read it right, after leaving mid countdown and joining again, the
> > next switch with a countdown now gets past mac80211 and runs into this in
> > ath9k_htc_channel_switch_beacon():
> >
> You read it right, I reproduced it on an AR9271 with this patch. A mesh
> point hits the same WARN already without it, since ieee80211_stop_mesh()
> aborts the switch the same way.
>
> Dropping csa_vif whenever beaconing stops is too much though: off
> channel, e.g. a scan during the countdown, beaconing stops with the
> switch still active, and the switch then never completes. So the fix
> drops it only when the switch is no longer active, sent as "wifi:
> ath9k_htc: clear csa_vif when a switch is aborted". This patch should
> go in with or after that one.
>
> Mehmet
>
Thanks for sending the patch, for this one:
Reviewed-by: Luka Gejak <luka.gejak@linux.dev>
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-10-27 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 19:36 Mehmet Fide
2026-10-26 12:43 ` Luka Gejak
2026-10-26 15:25 ` Mehmet Fide
2026-10-27 10:01 ` Luka Gejak [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=5c3f973b90b90271771f6deaa8748f8ece50b370@linux.dev \
--to=luka.gejak@linux.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.com \
--cc=toke@toke.dk \
/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®