On Tue, Dec 17, 2013 at 1:49 PM, Sander Eikelenboom
<linux@xxxxxxxxxxxxxx> wrote:
>
> So if i combine the two .. it's essentially just a very bad idea to compile the wireless stuff in.
> It needs a access to a userland program at module load time, or it will block forever.
No, it's a very stupid module if it does that.
It should require the crda hook not at module load time, but at first
ifconfig time.
We've had bugs like this before. Doing user-mode callbacks at module
loading time is a disaster exactly because it doesn't work well with
built-in modules.
The fact that those things apparently also don't time out or notice
when they fail seems to then just exacerbate the bad decision.
We have literally had this *exact* same issue with firmware loading.
Network drivers shouldn't try to load firmware at module load time.
Same deal.
What's the broken path? Is this driver-specific, or is it generic to
the 802.11 code?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
