On Thu, Nov 13, 2014 at 10:48:11PM +0900, Marcel Holtmann wrote:
> Hi Stanislaw,
> 
> >>> With the alias cfg80211 module is loaded on systems without the wireless
> >>> hardware when user-space use nl80211 to discover if there are wireless
> >>> devices, what is considered as resources wastage. On systems with
> >>> wireless hardware cfg80211 module will be loaded anyway.
> >>> 
> >>> Cc: Marcel Holtmann <[email protected]>
> >>> Signed-off-by: Stanislaw Gruszka <[email protected]>
> >>> ---
> >>> net/wireless/core.c | 1 -
> >>> 1 file changed, 1 deletion(-)
> >>> 
> >>> diff --git a/net/wireless/core.c b/net/wireless/core.c
> >>> index a4d2792..badcabe 100644
> >>> --- a/net/wireless/core.c
> >>> +++ b/net/wireless/core.c
> >>> @@ -34,7 +34,6 @@
> >>> MODULE_AUTHOR("Johannes Berg");
> >>> MODULE_LICENSE("GPL");
> >>> MODULE_DESCRIPTION("wireless configuration support");
> >>> -MODULE_ALIAS_GENL_FAMILY(NL80211_GENL_NAME);
> >> 
> >> NAK.
> >> 
> >> We want to auto-load cfg80211 when userspace asked for nl80211 netlink 
> >> family.
> > 
> > Could you elaborate more why?
> 
> you want to talk to the nl80211 family. The kernel has a module that allows 
> you to talk to this family. So let it load the netlink family.

This is not strictly true. User-space does not wan to talk to nl80211, it
wants to talk to hardware via nl80211. If there is no hardware, there is
nothing to talk to.

> If you do not want cfg80211 loaded, then fix NetworkManager and not hack the 
> kernel. NetworkManager asks to talk to nl80211 in the first place. That one 
> is causing the loading of cfg80211 module.
> 
> You can also de-install the NetworkManager module for wireless, right. Then 
> none of this should happen. Seriously, fix your userspace and do not blame 
> the kernel for a perfect valid behavior.

Maybe this is perfectly valid behaviour, but if it makes perfect sense
is dubious.

Stanislaw 
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to