Am Dienstag 05 Juli 2011, 03:24:14 schrieb Tetsuo Handa: > Richard Weinberger wrote: > > With MAX_KMOD_CONCURRENT=3 it takes only a few seconds until > > the modprobe storm ends. > > OK. Many years ago, I got a few reports that the kernel panics after > printing > > request_module: runaway loop modprobe binfmt-464c > > line. This was because they installed by error a binary x86_32 kernel rpm > on x86_64 userland tools. So, this error is not specific to UML. > > > How shall we proceed? > > Applying my ad-hoc patch > > or lowering MAX_KMOD_CONCURRENT? > > What about disallowing request_module() for ____call_usermodehelper() > threads? This patch helps. But IMHO adding a new attribute to task_struct is a bit overkill. Why is your variant better than my strcmp() in fs/exec.c? Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
