* Andi Kleen | 2008-01-31 13:49:54 [+0100]: >On Thursday 31 January 2008 13:48:34 Sebastian Siewior wrote: >> * Andi Kleen | 2008-01-31 10:21:24 [+0100]: >> >> >FYI -- with a linus git kernel of yesterday or so I ran into a problem where >> >one cipher module (CBC) was compiled in and the rest modular. dm_crypt >> >could not resolve the cipher module until I turned it into a module. >> and dm_crypt itself was a module? > >I don't remember to be honest. Is it important? It could be possible that dm_crypt is trying to use the crypto API before it is initialized, but I doubt it. > >> >Also I found that cryptomanager is quite unhappy when CONFIG_KMOD >> >is not defined. Perhaps it should Kconfig select it? >> If you disable modules, than why should one module enable it? > >CONFIG_KMOD is not modules (that is CONFIG_MODULES), but module >autoloading. Ach, you right. This problem has every user of try_then_request_module() and I don't see anybody selecting CONFIG_KMOD in the kernel. >-Andi Sebastian - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
