public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Chua <jchua@fedex.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.51 ide module problem (fwd)
Date: Thu, 12 Dec 2002 18:54:35 +1100	[thread overview]
Message-ID: <20021212080110.E663A2C564@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 12 Dec 2002 14:22:02 +0800." <Pine.LNX.4.50.0212121419410.15261-100000@boston.corp.fedex.com>

In message <Pine.LNX.4.50.0212121419410.15261-100000@boston.corp.fedex.com> you
 write:
> 
> Rusty,
> 
> Any chance that module-init-tools-0.9.3 can be modified to stop looping
> when it detected it has repeated scanning the same module again?

I didn't see this report before, so it's the first I've heard of it.

> > 	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.

Actually, depmod should print out every dependency, so that modprobe
doesn't have to do the recursion check.

But yes, circular dependencies will screw it.

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

I'll test, and release a fix.

Thanks for the (indirect) bug report!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-12-12  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  6:22 2.5.51 ide module problem (fwd) Jeff Chua
2002-12-12  7:54 ` Rusty Russell [this message]
2002-12-12  9:48 ` Rusty Russell
2002-12-12 12:38   ` Alan Cox
2002-12-13  1:35     ` Rusty Russell
2002-12-13 10:42       ` Alan Cox
2002-12-14  1:54   ` Jeff Chua
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14  6:22 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=20021212080110.E663A2C564@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox