From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Zaborowski <andrew.zaborowski@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT
Date: Wed, 04 Jan 2017 16:40:33 +0100 [thread overview]
Message-ID: <1483544433.7312.13.camel@sipsolutions.net> (raw)
In-Reply-To: <20161218002554.6362-1-andrew.zaborowski@intel.com> (sfid-20161218_013029_456399_B1802872)
> +++ b/net/wireless/mlme.c
> @@ -340,6 +340,8 @@ int cfg80211_mlme_deauth(struct
> cfg80211_registered_device *rdev,
>
> ASSERT_WDEV_LOCK(wdev);
>
> + wdev->conn_owner_nlportid = 0;
Is this really correct? The deauth might not be to the current_bss, as
you can see in the following if statement:
> if (local_state_change &&
> (!wdev->current_bss ||
> !ether_addr_equal(wdev->current_bss->pub.bssid, bssid)))
It seems that perhaps this should go into some other place, perhaps
only be reset when current_bss is also reset to NULL?
> @@ -14539,13 +14554,21 @@ static int nl80211_netlink_notify(struct
> notifier_block * nb,
> spin_unlock(&rdev-
> >destroy_list_lock);
> schedule_work(&rdev->destroy_work);
> }
> - } else if (schedule_scan_stop) {
> +
> + continue;
> + }
This also doesn't seem right - the same socket could possibly own both
an interface and a connection? If the connection is on the same
interface you might not really want to do both - though it shouldn't
hurt if all the cancel_work is in the right place - but it could be a
different interface?
johannes
next prev parent reply other threads:[~2017-01-04 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 0:25 [PATCH v4] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT Andrew Zaborowski
2017-01-04 15:40 ` Johannes Berg [this message]
2017-01-04 20:35 ` Andrew Zaborowski
2017-01-05 9:56 ` Johannes Berg
2017-01-06 19:24 ` 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=1483544433.7312.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrew.zaborowski@intel.com \
--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.