Search Linux Wireless

RE: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx>, Luca Coelho <luca@xxxxxxxxx>, "johannes@xxxxxxxxxxxxxxxx" <johannes@xxxxxxxxxxxxxxxx>
Subject: RE: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
From: "Otcheretianski, Andrei" <andrei.otcheretianski@xxxxxxxxx>
Date: Tue, 27 Jun 2017 12:12:15 +0000
Accept-language: en-US
Cc: "linux-wireless@xxxxxxxxxxxxxxx" <linux-wireless@xxxxxxxxxxxxxxx>, "Coelho, Luciano" <luciano.coelho@xxxxxxxxx>
Dlp-product: dlpe-windows
Dlp-reaction: no-action
Dlp-version: 10.0.102.7
In-reply-to: <90201931-33b5-cf49-9734-a42856af3a36@broadcom.com>
References: <20170626165230.13971-1-luca@coelho.fi> <90201931-33b5-cf49-9734-a42856af3a36@broadcom.com>

> Almost there :-p Is the reference in NL80211_CMD_ADD_NAN_FUNCTION doc to
> NL80211_ATTR_SOCKET_OWNER still warranted?

I think yes. It explains where NAN events will go, and this is relevant only when you add functions.

>
> Regards,
> Arend

References:
- [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
  - From: Luca Coelho
- Re: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
  - From: Arend van Spriel

Prev by Date: Re: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
Next by Date: [PATCH 3.18 16/16] mac80211/wpa: use constant time memory comparison for MACs
Previous by thread: Re: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
Next by thread: Re: [PATCH v2] nl80211: Don't verify owner_nlportid on NAN commands
Index(es):
- Date
- Thread

[Index of Archives] [Linux Host AP] [ATH6KL] [Linux Wireless Personal Area Network] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Linux Kernel] [IDE] [Git] [Netfilter] [Bugtraq] [Yosemite Hiking] [MIPS Linux] [ARM Linux] [Linux RAID]

Powered by Linux