From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Andrew Zaborowski <andrew.zaborowski@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH][RFC] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT
Date: Wed, 7 Dec 2016 00:40:57 -0600 [thread overview]
Message-ID: <5847AEF9.90409@gmail.com> (raw)
In-Reply-To: <1481091301.4092.5.camel@sipsolutions.net>
Hi Johannes,
On 12/07/2016 12:15 AM, Johannes Berg wrote:
>
>> I'm afraid to consider what you're like when you _are_ 'super'
>> against something :)
>
> Why, that's easy, there wouldn't be a long discussion like that ;-)
lol
>
> No, this is the part you didn't understand. Simply authenticating
> doesn't actually create anything like a "link" to the AP. The only
Okay, but it is then a bit misleading that iw link reports us being
'connected' during this time for example.
> reason we keep the station entry around for a few seconds is that it
> *probably* will be used next to associate. But if you don't do that, or
> authenticate to some other AP, or do whatever else - nothing stops you
> from doing that. There's no connection, nothing really stays active
> except for this 5 second grace period to associate.
>
> So even if you crash here like in the example, there's nothing to clean
> up, a subsequent authentication attempt to the same or another AP will
> go through anyway.
>
> Therefore, there's nothing to "own" with an authentication attempt,
> since it doesn't actually keep any (permanent) state in the kernel, and
> keeping the station entry around is just an optimisation.
>
> I don't think it's worth trying to clean that up.
Fair enough. I think we can live with that since we're not using
CMD_AUTHENTICATE unless we need to roam using FT.
Regards,
-Denis
next prev parent reply other threads:[~2016-12-07 6:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 20:56 [PATCH][RFC] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT Andrew Zaborowski
2016-12-05 13:51 ` Johannes Berg
2016-12-05 14:55 ` Denis Kenzior
2016-12-05 14:58 ` Johannes Berg
2016-12-05 15:05 ` Denis Kenzior
2016-12-05 15:14 ` Johannes Berg
2016-12-05 15:32 ` Denis Kenzior
2016-12-06 7:16 ` Johannes Berg
2016-12-06 21:42 ` Denis Kenzior
2016-12-07 1:40 ` Andrew Zaborowski
2016-12-07 6:19 ` Johannes Berg
2016-12-07 9:49 ` Andrew Zaborowski
2016-12-07 6:15 ` Johannes Berg
2016-12-07 6:40 ` Denis Kenzior [this message]
2016-12-07 6:48 ` Johannes Berg
2016-12-07 7:07 ` Denis Kenzior
2016-12-07 7:38 ` Johannes Berg
2016-12-05 15:40 ` Marcel Holtmann
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=5847AEF9.90409@gmail.com \
--to=denkenz@gmail.com \
--cc=andrew.zaborowski@intel.com \
--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 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.