From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH] station: Move netconfig_reset() to common path
Date: Wed, 29 Sep 2021 17:07:26 -0500 [thread overview]
Message-ID: <2e596fd9-c849-e3b2-f296-6fffadef29af@gmail.com> (raw)
In-Reply-To: CAOq732KHRh4HvDnGaKXqe4SPH=K=Hju=GJ-i9OJwap=jXQcKGA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Hi Andrew,
On 9/29/21 5:05 PM, Andrew Zaborowski wrote:
> Hi Denis,
>
> On Wed, 29 Sept 2021 at 22:06, Denis Kenzior <denkenz(a)gmail.com> wrote:
>> On 9/29/21 11:42 AM, Andrew Zaborowski wrote:
>>> Move the netconfig_reset calls to inside
>>> station_reset_connection_state() instead of having each caller do
>>
>> This is on purpose. There should be no need to call netconfig_reset if
>> netconfig_configure wasn't called in the first place.
>
> In this case it *was* called, then for some reason the driver
> deauthenticated when we requested a scan (from_ap is false), netdev
That would be useful info and should be in the commit description ;)
> emitted a NETDEV_EVENT_DISCONNECT_BY_SME and we end up in
> station_connect_cb. You're right in that station_connect_cb also
Then that sounds like a bug or another side-effect of delaying the CONNECTED
state until netconfig is done. NETDEV_EVENT_DISCONNECT_BY_SME should result
in station_disassociated() and not station_connect_cb()
> handles failures before the netconfig_configure call, so if you want
> to avoid the potentially unneeded netconfig_reset() I can move it
> inside station_disconnect_event to avoid bigger changes.
Regards,
-Denis
next reply other threads:[~2021-09-29 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 22:07 Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-29 23:14 [PATCH] station: Move netconfig_reset() to common path Andrew Zaborowski
2021-09-29 23:09 Denis Kenzior
2021-09-29 22:46 Denis Kenzior
2021-09-29 22:20 Andrew Zaborowski
2021-09-29 22:05 Andrew Zaborowski
2021-09-29 19:51 Denis Kenzior
2021-09-29 16:42 Andrew Zaborowski
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=2e596fd9-c849-e3b2-f296-6fffadef29af@gmail.com \
--to=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