From: "Gordon Farquharson" <gordonfarquharson@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
davem@davemloft.net
Subject: Re: physmap and "request_module: runaway loop modprobe net-pf-1"
Date: Wed, 23 Apr 2008 22:01:07 -0600 [thread overview]
Message-ID: <97a0a9ac0804232101i71bfff22o723e2aaa80b09c2f@mail.gmail.com> (raw)
In-Reply-To: <1208867831.9212.582.camel@pmac.infradead.org>
Hi David
On Tue, Apr 22, 2008 at 6:37 AM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Tue, 2008-03-11 at 22:59 -0700, Andrew Morton wrote:
>
> > Now, af_unix_init() uses module_init(), which is really __initcall(), which
> > is really device_initcall() (ug, don't ask).
>
> ... which is really __define_initcall("6", ...);.
>
>
> > So you can do what you're sugesting here by locating the caller/callers of
> > parse_mtd_partitions() and marking them late_initcall().
>
> Better still, just initialise af_unix earlier so that it's there before
> any normal drivers which happen to call request_module(). Since core
> network stuff is initialised with subsys_initcall() which is really
> __define_initcall("4", ...), we can initialise af_unix with
> fs_initcall() which is really __define_initcall("5", ...).
I tested the patch you sent. It fixes the runaway modprobe messages,
but I get a modprobe error (see below) with the Debian kernel I used
to test the patch because modules.dep does not exist in the initramfs
(should it?). In my kernel config, I did not enable
CONFIG_MTD_CMDLINE_PARTS and I set CONFIG_MTD_REDBOOT_PARTS=m but the
redboot module was not included in the initramfs so it could not be
loaded, hence the messages saying that the parsing schemes are not
available.
[ 4.790000] physmap platform flash device: 00080000 at f0000000
[ 4.800000] Found: ST M29W400DB
[ 4.800000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
[ 4.810000] number of JEDEC chips: 1
[ 4.810000] cfi_cmdset_0002: Disabling erase-suspend-program due to
code brokenness.
modprobe: FATAL: Could not load
/lib/modules/2.6.25-trunk-iop32x/modules.dep: No such file or
directory
[ 4.900000] cmdlinepart partition parsing not available
modprobe: FATAL: Could not load
/lib/modules/2.6.25-trunk-iop32x/modules.dep: No such file or
directory
[ 4.970000] RedBoot partition parsing not available
I guess the question is which patch (if either) is more appealing.
Gordon
--
Gordon Farquharson
GnuPG Key ID: 32D6D676
WARNING: multiple messages have this Message-ID (diff)
From: "Gordon Farquharson" <gordonfarquharson@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: physmap and "request_module: runaway loop modprobe net-pf-1"
Date: Wed, 23 Apr 2008 22:01:07 -0600 [thread overview]
Message-ID: <97a0a9ac0804232101i71bfff22o723e2aaa80b09c2f@mail.gmail.com> (raw)
In-Reply-To: <1208867831.9212.582.camel@pmac.infradead.org>
Hi David
On Tue, Apr 22, 2008 at 6:37 AM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Tue, 2008-03-11 at 22:59 -0700, Andrew Morton wrote:
>
> > Now, af_unix_init() uses module_init(), which is really __initcall(), which
> > is really device_initcall() (ug, don't ask).
>
> ... which is really __define_initcall("6", ...);.
>
>
> > So you can do what you're sugesting here by locating the caller/callers of
> > parse_mtd_partitions() and marking them late_initcall().
>
> Better still, just initialise af_unix earlier so that it's there before
> any normal drivers which happen to call request_module(). Since core
> network stuff is initialised with subsys_initcall() which is really
> __define_initcall("4", ...), we can initialise af_unix with
> fs_initcall() which is really __define_initcall("5", ...).
I tested the patch you sent. It fixes the runaway modprobe messages,
but I get a modprobe error (see below) with the Debian kernel I used
to test the patch because modules.dep does not exist in the initramfs
(should it?). In my kernel config, I did not enable
CONFIG_MTD_CMDLINE_PARTS and I set CONFIG_MTD_REDBOOT_PARTS=m but the
redboot module was not included in the initramfs so it could not be
loaded, hence the messages saying that the parsing schemes are not
available.
[ 4.790000] physmap platform flash device: 00080000 at f0000000
[ 4.800000] Found: ST M29W400DB
[ 4.800000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
[ 4.810000] number of JEDEC chips: 1
[ 4.810000] cfi_cmdset_0002: Disabling erase-suspend-program due to
code brokenness.
modprobe: FATAL: Could not load
/lib/modules/2.6.25-trunk-iop32x/modules.dep: No such file or
directory
[ 4.900000] cmdlinepart partition parsing not available
modprobe: FATAL: Could not load
/lib/modules/2.6.25-trunk-iop32x/modules.dep: No such file or
directory
[ 4.970000] RedBoot partition parsing not available
I guess the question is which patch (if either) is more appealing.
Gordon
--
Gordon Farquharson
GnuPG Key ID: 32D6D676
next prev parent reply other threads:[~2008-04-24 4:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 5:35 physmap and "request_module: runaway loop modprobe net-pf-1" Gordon Farquharson
2008-03-12 5:59 ` Andrew Morton
2008-03-12 5:59 ` Andrew Morton
2008-03-12 7:06 ` Gordon Farquharson
2008-03-12 7:06 ` Gordon Farquharson
2008-03-12 7:19 ` Andrew Morton
2008-03-12 7:19 ` Andrew Morton
2008-03-12 7:36 ` David Woodhouse
2008-03-12 7:36 ` David Woodhouse
2008-04-22 12:37 ` David Woodhouse
2008-04-22 12:37 ` David Woodhouse
2008-04-24 4:01 ` Gordon Farquharson [this message]
2008-04-24 4:01 ` Gordon Farquharson
2008-04-24 5:49 ` David Woodhouse
2008-04-24 5:49 ` David Woodhouse
2008-04-24 6:10 ` David Miller
2008-04-24 6:10 ` David Miller
2008-04-24 7:16 ` David Woodhouse
2008-04-24 7:16 ` David Woodhouse
2008-04-24 7:20 ` David Miller
2008-04-24 7:20 ` David Miller
2008-04-24 7:24 ` David Woodhouse
2008-04-24 7:24 ` David Woodhouse
2008-04-24 7:58 ` David Miller
2008-04-24 7:58 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97a0a9ac0804232101i71bfff22o723e2aaa80b09c2f@mail.gmail.com \
--to=gordonfarquharson@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.