All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: jchua@fedex.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.51 ide module problem
Date: Tue, 10 Dec 2002 22:50:20 -0800	[thread overview]
Message-ID: <200212110650.WAA13780@adam.yggdrasil.com> (raw)

>depmod will ecounter "Segmentation fault" if the ide.ko and ide-io.ps
>modules are in /lib/modules/2.5.51/kernel

	I think the new depmod recurses infinitely when it encounters
circular dependencies.  It eventually segfaults and leaves a huge
modules.dep file from the infinite loop.  If you look at the final
huge line in that file, you can see where the loop occurred.

	depmod has no need to do any recursion, since it only needs
to determine the immediate dependencies of each module.  However,
noticing such loops and printing them out would be a handy feature.

	I use IDE as a module, but I had to change the Makefile to
build a big ide-mod.o from most of the core objects rather than
allowing each one to be its own module.  I believe I posted IDE
modularization patches at least once a couple of months ago, but it
seems to have fallen between the cracks.  I could repost it if need
be, although I have not yet booted 2.5.51.

	Also note that I have not used the in kernel-based module
loader recently, as I have been patching my kernels to use the user
level module code.  I am planning to try the kernel-base module loader
in 2.5.51 once I fix other problems it has finding the root device
under devfs.  So, it's remotely possible that you may also see module
problems that I've missed.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-12-11  6:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11  6:50 Adam J. Richter [this message]
2002-12-11  7:07 ` 2.5.51 ide module problem Jeff Chua
2002-12-11  8:41   ` Adam J. Richter
     [not found]     ` <Pine.LNX.4.50.0212111711180.4632-200000@boston.corp.fedex.com>
2002-12-13  7:59       ` Adam J. Richter
2002-12-13 10:31         ` Alan Cox
2002-12-14  6:45         ` Jeff Chua
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 14:18 Adam J. Richter
2002-12-18 14:14 Adam J. Richter
2002-12-18 16:07 ` Alan Cox
2002-12-18 19:50   ` Jeff Chua
2002-12-18 22:43     ` Alan Cox
2002-12-18 22:06       ` Andre Hedrick
2002-12-11  5:49 Jeff Chua

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=200212110650.WAA13780@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=jchua@fedex.com \
    --cc=linux-kernel@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.