I am currently rebuilding with the patch below applied to see if that
will fix the issue. It feels very much like a workaround though, and I
fear that even if it does the job other problems might pop up elsewhere
for other people. Perhaps you might consider posting the original
patches to LKML for some more eyeballing?
--- ../api.c 2010-08-02 00:11:14.000000000 +0200
+++ crypto/api.c 2010-10-15 10:19:55.306433001 +0200
@@ -15,8 +15,10 @@
*
*/
+#include <linux/async.h>
#include <linux/err.h>
#include <linux/errno.h>
+#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/kmod.h>
#include <linux/module.h>
@@ -215,6 +217,7 @@
mask &= ~(CRYPTO_ALG_LARVAL | CRYPTO_ALG_DEAD);
type &= mask;
+ async_synchronize_full_domain(&populate_rootfs_domain);
alg = crypto_alg_lookup(name, type, mask);
if (!alg) {
request_module("%s", name);
@@ -239,6 +242,7 @@
ok = blocking_notifier_call_chain(&crypto_chain, val, v);
if (ok == NOTIFY_DONE) {
+ async_synchronize_full_domain(&populate_rootfs_domain);
request_module("cryptomgr");
ok = blocking_notifier_call_chain(&crypto_chain, val, v);
}
--
Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep
https://bugs.launchpad.net/bugs/642421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
