From: Felix Fietkau <nbd@nbd.name>
To: Alexander Wetzel <alexander@wetzel-home.de>,
linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Ensure vif queues are operational after start
Date: Thu, 15 Sep 2022 18:18:39 +0200 [thread overview]
Message-ID: <26e9ae91-8e13-df45-815c-cb45c1911032@nbd.name> (raw)
In-Reply-To: <20220915130946.302803-1-alexander@wetzel-home.de>
On 15.09.22 15:09, Alexander Wetzel wrote:
> Make sure local->queue_stop_reasons and vif.txqs_stopped stay in sync.
>
> When a new vif is created the queues may end up in an inconsistent state
> and be inoperable:
> Communication not using iTXQ will work, allowing to e.g. complete the
> association. But the 4-way handshake will time out. The sta will not
> send out any skbs queued in iTXQs.
>
> All normal attempts to start the queues will fail when reaching this
> state.
> local->queue_stop_reasons will have marked all queues as operational but
> vif.txqs_stopped will still be set, creating an inconsistent internal
> state.
>
> In reality this seems to be race between the mac80211 function
> ieee80211_do_open() setting SDATA_STATE_RUNNING and the wake_txqs_tasklet:
> Depending on the driver and the timing the queues may end up to be
> operational or not.
>
> Cc: stable@vger.kernel.org
> Fixes: f856373e2f31 ("wifi: mac80211: do not wake queues on a vif that is being stopped")
> Signed-off-by: Alexander Wetzel <alexander@wetzel-home.de>
Acked-by: Felix Fietkau <nbd@nbd.name>
Thanks for figuring this one out,
- Felix
next prev parent reply other threads:[~2022-09-15 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 13:09 [PATCH] mac80211: Ensure vif queues are operational after start Alexander Wetzel
2022-09-15 16:18 ` Felix Fietkau [this message]
2022-09-15 19:59 ` Alexander Wetzel
2022-09-15 20:06 ` Alexander Wetzel
2022-09-15 20:39 ` Ben Greear
2022-09-16 16:38 ` Alexander Wetzel
2022-09-16 17:10 ` Ben Greear
2022-09-16 5:38 ` Kalle Valo
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=26e9ae91-8e13-df45-815c-cb45c1911032@nbd.name \
--to=nbd@nbd.name \
--cc=alexander@wetzel-home.de \
--cc=johannes@sipsolutions.net \
--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