Richard Weinberger wrote:
> > That's strange... Would you show us printk() output like
> >
> > printk(KERN_INFO "Calling request_module()\n");
> > request_module("binfmt-%04x", *(unsigned short *)(&bprm->buf[2]));
> > printk(KERN_INFO "Returned from request_module()\n");
> >
> > for demonstrating that __request_module() cannot stop at
> > MAX_KMOD_CONCURRENT levels of nesting?
>
> There you go!
> http://userweb.kernel.org/~rw/boot.log
>
> I did not count all messages, but they are more than 50. :-)
Thank you.
$ grep -F 'Calling request_module()' boot.log | wc -l
25819
$ grep -F 'Returned from request_module()' boot.log | wc -l
25770
So, __request_module() is stopping at MAX_KMOD_CONCURRENT levels
of nesting. Eventually the process that triggered the first
request_module() will return from search_binary_handler().
I don't think this is an infinite loop inside search_binary_handler().
But it would look like an infinite loop bug if the caller of execve()
repeats forever. Printing additional information like
printk(KERN_INFO "Calling request_module() %s %d %s %d %d\n", current->comm,
current->pid, bprm->filename, bprm->argc, bprm->envc);
would help.
--
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
