From: Jan Hendrik Farr <kernel@jfarr.cc>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: James Prestwood <prestwoj@gmail.com>,
linux-wireless@vger.kernel.org,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
iwd@lists.linux.dev, Denis Kenzior <denkenz@gmail.com>
Subject: Re: wifi: iwlwifi: SAE fails when AP sends confirm before STA
Date: Tue, 13 May 2025 19:36:19 +0200 [thread overview]
Message-ID: <aCODE231NMCQ48xu@archlinux> (raw)
In-Reply-To: <047456d40bc42248a6ba1b76d630d5d82b857bf1.camel@sipsolutions.net>
On 13 19:07:30, Johannes Berg wrote:
> On Tue, 2025-05-13 at 18:33 +0200, Jan Hendrik Farr wrote:
> > > I don't think this is really the right fix, but it might help:
> > > https://p.sipsolutions.net/e852565303ad878b.txt
> >
> > Unfortunately this does not fix it.
> >
> > Attached another capture (and trace, etc)
>
> Hm. Yeah, I missed the second path that goes there in this case ...
>
> https://p.sipsolutions.net/0c145f72fdec3cf5.txt
This work!
Interestingly though, now the order is always:
1. client commit
2. AP commit
3. client confirm
4. AP confirm
It is now only ~5.3 ms between AP commit and client confirm vs
~21.2 ms before.
Do you have an explanation why this patch would change the timing?
So this test doesn't proof that it would work with the order the other way
around. Maybe I should try making iwd sleep while generating the commit.
Best Regards
Jan
>
> johannes
next prev parent reply other threads:[~2025-05-13 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 12:24 wifi: iwlwifi: SAE fails when AP sends confirm before STA Jan Hendrik Farr
2025-05-09 13:12 ` James Prestwood
2025-05-09 13:45 ` Jan Hendrik Farr
2025-05-09 14:10 ` James Prestwood
2025-05-09 15:37 ` Jan Hendrik Farr
2025-05-09 18:39 ` Johannes Berg
2025-05-09 20:42 ` Jan Hendrik Farr
2025-05-12 20:52 ` Jan Hendrik Farr
2025-05-12 21:20 ` Jan Hendrik Farr
2025-05-13 7:35 ` Johannes Berg
2025-05-13 11:29 ` Jan Hendrik Farr
2025-05-13 11:46 ` Johannes Berg
2025-05-13 11:56 ` Jan Hendrik Farr
2025-05-13 16:33 ` Jan Hendrik Farr
2025-05-13 17:07 ` Johannes Berg
2025-05-13 17:36 ` Jan Hendrik Farr [this message]
2025-05-13 17:45 ` Johannes Berg
2025-05-15 12:36 ` Jan Hendrik Farr
2025-05-15 12:40 ` Johannes Berg
2025-05-13 14:03 ` Denis Kenzior
2025-05-13 14:19 ` Jan Hendrik Farr
2025-05-13 14:25 ` Jan Hendrik Farr
2025-05-13 14:53 ` Johannes Berg
2025-05-13 15:04 ` Denis Kenzior
2025-05-13 15:14 ` Johannes Berg
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=aCODE231NMCQ48xu@archlinux \
--to=kernel@jfarr.cc \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=prestwoj@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.