Re: Runaway loop with the current git.

[Herbert Xu]

Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
>> This modprobe process does try to log an error, accesses /dev/console,
>> which is not initialized in the kernel at that time, and the kernel
>> module loader tries the load a module to support dev_t 5:1, which
>> again runs modprobe, and ...
> 
> So we have a buggy modprobe... 

FWIW the crypto layer is doing what is intended.  The algorithm
testing infrastructure in the cryptomgr module is optional and
only used when algorithms are registered.  That's why it sits
in its own module which is loaded by the algorithm registration
code which still functions if the module is absent or fails to
load.

In any case the loop itself does not involve any crypto components
so I don't think making changes in the crypto layer is going to
make this go away forever as anyone calling request_module early
enough will get into this loop.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/