public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: "iwd@lists.linux.dev" <iwd@lists.linux.dev>,
	"Pedro André" <PEDA@bang-olufsen.dk>
Subject: Re: [PATCH] netdev: handle disconnect event during the 4-way handshake
Date: Wed, 17 Jul 2024 14:18:42 -0700	[thread overview]
Message-ID: <0bcb2fdf-69c2-4bc3-84ce-52b72d60836b@gmail.com> (raw)
In-Reply-To: <egk54l4s2ylywom72plctncrjbvwvd4h3ddcrnlnbqecl5f2l4@pd7ojuwyivf2>

Hi Alvin,

On 7/17/24 12:35 PM, Alvin Šipraga wrote:
> Hi James,
>
> On Wed, Jul 17, 2024 at 08:02:17AM GMT, James Prestwood wrote:
>> + CC Alvin
>>
>> You had originally reported [1] a similar issue but it was unclear exactly
>> what was happening at the time. I believe this is the same problem. This may
>> not be the final version of a fix, but I wanted to CC you in case you still
>> were seeing this and wanted to test it.
>>
>> [1] https://lore.kernel.org/iwd/20230403141927.235014-1-alvin@pqrs.dk/
> It's been a while since I dealt with this problem, and in the mean time
> we have been using the original patch I sent to the list as seen in your
> link. Unfortunately I don't recall how I reproduced this issue, but
> maybe my colleague Pedro (+cc) remembers.
>
> Regardless, a static code analysis suggests that your patch yields the
> same result, so I think this is good - one less patch for us to apply :)
>
> Do you have some easily communicable steps to reproduce this issue on
> your end?

I was able to write an autotest for it that took that code path. Its 
basically just as you thought from your previous thread. If a deauth 
frame comes in during the 4-way handshake or key settings during a 
reassociate roam it triggers that "Unexpected disconnect" path in 
station, causing IWD to hang up and not clean up its state.

I just wanted to check in with you that its being fixed. Denis and I 
have been discussing it and my ML patch still isn't quite how he wants 
it, but we think we know how it should be handled.

Thanks,
James

>
> Thanks for following up on this!
>
> Kind regards,
> Alvin

      reply	other threads:[~2024-07-17 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 14:00 [PATCH] netdev: handle disconnect event during the 4-way handshake James Prestwood
2024-07-17 16:33 ` Denis Kenzior
     [not found] ` <a3c34f70-9620-4a27-ac76-ab55b2bc636c@gmail.com>
2024-07-17 19:35   ` Alvin Šipraga
2024-07-17 21:18     ` James Prestwood [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=0bcb2fdf-69c2-4bc3-84ce-52b72d60836b@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=ALSI@bang-olufsen.dk \
    --cc=PEDA@bang-olufsen.dk \
    --cc=iwd@lists.linux.dev \
    /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