physmap and "request_module: runaway loop modprobe net-pf-1"

David Miller davem at davemloft.net
Thu Apr 24 03:20:38 EDT 2008


From: David Woodhouse <dwmw2 at infradead.org>
Date: Thu, 24 Apr 2008 08:16:39 +0100

> On Wed, 2008-04-23 at 23:10 -0700, David Miller wrote:
> > From: David Woodhouse <dwmw2 at infradead.org>
> > Date: Thu, 24 Apr 2008 06:49:03 +0100
> > 
> > > On Wed, 2008-04-23 at 22:01 -0600, Gordon Farquharson wrote:
> > > > I guess the question is which patch (if either) is more appealing.
> > > 
> > > I definitely think we should initialise AF_UNIX sockets earlier. At
> > > least request_module() _can_ work then, if you want it to and you set up
> > > userspace accordingly.
> > 
> > I'm not so sure, for example, what if AF_UNIX is built modular?
> 
> I believe that as long as you include it in your initrd, it'll get
> loaded on demand and all will be well. The first request_module() call
> will trigger a request_module(af_unix), which will succeed.

But won't the request_module() for AF_UNIX spit out that warning too?

Actually, I think I need a clarification.  It is the modular loader
utility in userspace which is trying to open up AF_UNIX sockets,
right?



More information about the linux-mtd mailing list