Linux wireless drivers development
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: andcov23@gmail.com, Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
	Kavita Kavita <kavita.kavita@oss.qualcomm.com>,
	Sai Pratyusha Magam <sai.magam@oss.qualcomm.com>
Subject: Re: [PATCH] wifi: mac80211: defer AP-side FT key upload until association
Date: Tue, 11 Aug 2026 09:38:43 -0700	[thread overview]
Message-ID: <219ac494-deb2-41f7-a762-7b5e666499e3@gmail.com> (raw)
In-Reply-To: <20260730161531.3535100-1-andcov23@gmail.com>

Hi Andrea,

On 7/30/26 9:14 AM, andcov23@gmail.com wrote:
> From: Andrea Covelli <andcov23@gmail.com>
>
> During an AP-side Fast Transition, hostapd may install the PTK after
> creating a station entry but before marking it associated. The ASSOC gate
> in ieee80211_add_key() rejects the request with -ENOENT, producing:
>
>    nl80211: kernel reports: key addition failed
>
> Userspace may retry after association, but this race can instead break
> the roam, particularly with PMF.

How does this present itself on the station when this happens? I'm 
curious because over the years I've seen strange behavior from basically 
all vendors of access points like:

- Mysterious association timeouts despite good RSSI/utilization.
- Denied FT associations with reason code 53
- Successful FT roams immediately followed by a deauth with reason code 
6, 7, or 9.

I know the above could be from any host of issues, but I'm mostly 
curious what the client sees with this specific FT key upload failure.

Thanks,

James


  parent reply	other threads:[~2026-08-11 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 16:14 [PATCH] wifi: mac80211: defer AP-side FT key upload until association andcov23
2026-07-30 16:21 ` Johannes Berg
2026-07-30 17:00   ` Andrea Covelli
2026-07-30 18:54     ` Johannes Berg
2026-08-03 22:30       ` Andrea Covelli
2026-08-11 15:42         ` Andrea Covelli
2026-08-11 16:38 ` James Prestwood [this message]
2026-08-11 17:35   ` Andrea Covelli
2026-08-11 17:44     ` James Prestwood
2026-08-11 18:25       ` Andrea Covelli
2026-08-11 18:36         ` James Prestwood

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=219ac494-deb2-41f7-a762-7b5e666499e3@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=andcov23@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kavita.kavita@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sai.magam@oss.qualcomm.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