From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Ivanov <dmitrijs.ivanovs@ubnt.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] Check protocol number in nl80211 netlink socket release notification handler.
Date: Thu, 07 Apr 2016 09:36:35 +0200 [thread overview]
Message-ID: <1460014595.27154.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20160406172318.f6fec91145578157c500737c@ubnt.com> (sfid-20160406_162324_890477_45237117)
On Wed, 2016-04-06 at 17:23 +0300, Dmitry Ivanov wrote:
> This patch corrects the problem where non-privileged user can create
> netlink socket with the same port_id as used by hostapd but different
> protocol number. Upon close() or process termination, a notification
> is
> sent to nl80211 subsystem which will destroy virtual wireless
> network
> interfaces created by hostapd like it just died but in fact hostapd
> is
> still running. This is possible because port_id is unique within
> particular
> protocol number only.
>
Applied.
johannes
prev parent reply other threads:[~2016-04-07 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 14:23 [PATCH 2/2] Check protocol number in nl80211 netlink socket release notification handler Dmitry Ivanov
2016-04-07 7:36 ` Johannes Berg [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=1460014595.27154.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dmitrijs.ivanovs@ubnt.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 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).