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: Tue, 6 Dec 2016 15:42:47 -0600 [thread overview]
Message-ID: <584730D7.2020708@gmail.com> (raw)
In-Reply-To: <1481008560.6610.3.camel@sipsolutions.net>
Hi Johannes,
On 12/06/2016 01:16 AM, Johannes Berg wrote:
> On Mon, 2016-12-05 at 09:32 -0600, Denis Kenzior wrote:
>
>> To what purpose? That's like saying that maybe a socket should be
>> kept open in case an application crashes.
>
> That socket would be useless, so no, that's not comparable at all. It's
> more like saying the disk should be unmounted once 'mount' exits ;-)
>
Except the kernel doesn't want to reconfigure mount parameters every
15-30 minutes. So no, its not like 'mount' at all ;) But I digress, I
can see that we won't agree here. But we still would like the kernel to
clean up nicely if stuff hits the fan.
> Anyway ... I'm not even super against this patch, but you need to fix
I'm afraid to consider what you're like when you _are_ 'super' against
something :)
> things:
> * this is actually wrong for authenticate - I'll let you figure out
> why by yourself
So here's a quick test, with the client triggering authenticate, then
crashing:
< Request: Authenticate (0x25) len 52 [ack] 362.339712
Interface Index: 3 (0x00000003)
Wiphy Frequency: 2417 (0x00000971)
MAC Address <snip>
SSID: len 9
<snip>
Auth Type: 0 (0x00000000)
> Event: New Station (0x13) len 32 362.341337
Interface Index: 3 (0x00000003)
> Response: Authenticate (0x25) len 4 362.341860
Status: Success (0)
> Event: Authenticate (0x25) len 64 362.343640
Wiphy: 0 (0x00000000)
Interface Index: 3 (0x00000003)
> Event: Del Station (0x14) len 1144 367.442024
Interface Index: 3 (0x00000003)
MAC Address <snip>
Pay attention to the time stamps. The del station event comes in 5
seconds or so after our client has aborted. So for 5 seconds we have an
unmanaged link to some AP. It would be nice if the authentication was
aborted as soon as we crash.
So again, why do you say that SOCKET_OWNER is 'wrong' for authenticate?
Or do you mean something else?
> * you need to teach people to write useful commit messages
The commit description in this patch was lacking. We both agree here.
Regards,
-Denis
next prev parent reply other threads:[~2016-12-06 22:00 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 [this message]
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
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=584730D7.2020708@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).