All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Module unloading policy (should be killed from .config ?)
Date: Thu, 2 Sep 2004 00:23:25 +0100	[thread overview]
Message-ID: <20040901232325.GA31943@redhat.com> (raw)
In-Reply-To: <1094079597l.8614l.0l@werewolf.able.es>

On Wed, Sep 01, 2004 at 10:59:57PM +0000, J.A. Magallon wrote:
 > Hi all...
 > 
 > Since 2.6.8.1-mm3, my system hangs when I modprobe -r ipt_MASQUERADE
 > (yup, you guessed, its an SMP box). Just locks hard.
 > 
 > A kernel build without module unloading seems to work. I heard about
 > module unloading not being safe, but this is the first time it hits me
 > seriously.

I wrote a script a while ago that modprobe'd & rmmod'd every module
it could find. Results weren't pretty.

Lessons learned:
- lots of driver writers don't take into consideration the fact the hardware
  might not be present when the driver does probing.
- Those that do, fail to clean up properly in this case.
- A lot of drivers leave junk in sysfs/procfs after rmmod which causes
  great fun for the next driver that gets loaded that uses the same subsystems.

It's been a few months since I last ran that script, but I'll bet
the results today aren't much better than they were back then
despite a bunch of problems I reported getting fixed.

		Dave


      reply	other threads:[~2004-09-01 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 22:59 Module unloading policy (should be killed from .config ?) J.A. Magallon
2004-09-01 23:23 ` Dave Jones [this message]

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=20040901232325.GA31943@redhat.com \
    --to=davej@redhat.com \
    --cc=jamagallon@able.es \
    --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.