linux-kernel - Re: [PATCH] net-sysfs: Add entry for nl80211 interface type

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <51704721.2020001@broadcom.com>
Date:	Thu, 18 Apr 2013 21:18:57 +0200
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Marcel Holtmann" <marcel@...tmann.org>
cc:	"Bing Zhao" <bzhao@...vell.com>,
	"linux-netdev@...r.kernel.org" <linux-netdev@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Paul Stewart" <pstew@...omium.org>
Subject: Re: [PATCH] net-sysfs: Add entry for nl80211 interface type

On 04/18/2013 09:10 PM, Marcel Holtmann wrote:
> Hi Bing,
>
>>>> Add a "wireless/nl80211_iftype" entry in the net device sysfs
>>>> file structure to indicate the mode of the wireless device so
>>>> it can be discovered easily from userspace.
>>>
>>> I do question a little bit the usefulness for this one.
>>> It would only work on netdev and on wdev devices.
>>
>> It's true. That's why the new sysfs entry is added in the 'wireless' placeholder.
>>
>> /sys/class/net/ethX/wireless/
>>
>> For non-wireless dev, this won't apply.
>
> I have to correct myself. I meant it does NOT work for wdev. Please just go with nl80211 for this kind of information. It is the right way to handle it. Not some sysfs file.
>

I wanted to correct you on P2P but that would be diverging from the real 
message. Totally agreeing. Why add another user-space API when the 
nl80211 API can provide the information.

Gr. AvS


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/