netdev - Re: RFC: always enable MAC80211_RC

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]

Message-Id: <1214502942.4432.6.camel@localhost>
Date:	Thu, 26 Jun 2008 19:55:42 +0200
From:	Mattias Nissler <mattias.nissler@....de>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Johannes Berg <johannes@...solutions.net>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	Adrian Bunk <bunk@...sta.de>, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: RFC: always enable MAC80211_RC_PID?

Just what I remember about the discussion that led to the ugly Makefile.

On Tue, 2008-06-24 at 15:43 +0300, Adrian Bunk wrote:
> 
> Can we get one of either:
> - all selected mac80211 algorithms are built into the mac80211 module or

IIRC, this was originally voted against because this approach would
increase kernel image size or module size unnecessarily.

> - all selected mac80211 algorithms (including the default one) are in
>   their own modules

The argument against this was that there are people who don't compile in
module autoloading, can't figure out what's wrong (in spite of the
syslog message) and complain about wireless not working...

Anyway, I always liked any of the two things you suggested better than
what we have now.

Mattias

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html