netdev - Re: [PATCH] Add libertas_disablemesh module parameter to disable mesh interface

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 13 May 2011 15:26:24 +0200
From:	Sascha Silbe <silbe@...ivitycentral.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	linux-wireless <linux-wireless@...r.kernel.org>,
	devel <devel@...ts.laptop.org>, Dan Williams <dcbw@...hat.com>,
	John@...5-sascha.sascha.silbe.org,
	W.Linville@...5-sascha.sascha.silbe.org, <linville@...driver.com>,
	libertas-dev <libertas-dev@...ts.infradead.org>,
	netdev <netdev@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add libertas_disablemesh module parameter to disable mesh interface

Excerpts from Randy Dunlap's message of Wed May 11 19:00:30 +0200 2011:
> On Wed, 11 May 2011 14:52:34 +0200 Sascha Silbe wrote:
> 
> > This allows individual users and deployments to disable mesh support at
> > runtime, i.e. without having to build and maintain a custom kernel.
> 
> I guess a user could want to do this on a per-driver basis, but ISTM that
> it would be better to be something like a sysctl that applies to all (wireless)
> drivers.

AFAIK libertas is the only driver with a mesh implementation based on an
outdated 802.11s draft. To clarify, we could rename the parameter to
lbs_disable_olpcmesh (or just disable_olpcmesh).
Disabling 802.11s (latest draft) based mesh support is a separate
matter.

Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/

Download attachment "signature.asc" of type "application/pgp-signature" (495 bytes)