[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080424.002038.201593352.davem@davemloft.net>
Date: Thu, 24 Apr 2008 00:20:38 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dwmw2@...radead.org
Cc: gordonfarquharson@...il.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
netdev@...r.kernel.org
Subject: Re: physmap and "request_module: runaway loop modprobe net-pf-1"
From: David Woodhouse <dwmw2@...radead.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@...radead.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists