Re: pre-2.1.90.. (kmod fix)

Kirk Petersen (kirk@eidolon.speakeasy.org)
Wed, 11 Mar 1998 19:21:09 -0800

> The best way would probably be to drop the wait() call in kmod's kernel
> thread. Instead, let the parent do the loading and the child can do the
> next request. No waiting is necessary, as the parent will eventually die
> (it'll be reaped by init), thus the child will be reassigned to be a child
> of init (which is what we want).

I'm not sure that is possible. When request_module() is called,
it shouldn't return until modprobe has exit()ed. If it doesn't do the
wait(), it might return early and the module won't be ready.
What I'm trying now is to have the kmod daemon fork two
processes, one to do the modprobe and one to wait for it and notify
request_module() that it is done. The daemon just goes back to waiting
as soon as these processes have started.

-- 
Kirk Petersen
muppetlabs.com/~kirk/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu