mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Alex Buell <alex.buell@munted.org.uk>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Unused modules in 2.6.x
Date: Thu, 26 Feb 2009 09:48:57 -0500	[thread overview]
Message-ID: <20090226144856.GA23246@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20090226102939.42c92d34@lithium.local.net>

On Thu, Feb 26, 2009 at 10:29:39AM +0000, Alex Buell wrote:
> I'd have thought that hotplugging i.e. plug in an USB device in this
> case would load the modules as and when required. 
> 
> If the interface is up, then it shouldn't have to be unloaded, I think.
> I know I could just hack my initrds to remove any modules that I don't
> want loaded at bootup but surely... :-D

So how about if you plug in a usb drive, and the module is loaded to
provide disk access, but you aren't using it right now.  The next module
clean would remove the now unused module, and then when you do want to
use it, there is no longer any way to reach teh device, and since there
is no fixed device node to refer to that would cause the module to be
loaded again, now the device doesn't work.  That would be very annoying.

I think the big problem is that the kernel and the module utils can not
know if a module is actually being used or not since it is more a matter
of 'will it be needed' not 'is it in use right now'.

-- 
Len Sorensen

  reply	other threads:[~2009-02-26 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 17:52 Alex Buell
2009-02-25 18:40 ` Michael Tokarev
2009-02-26 10:29   ` Alex Buell
2009-02-26 14:48     ` Lennart Sorensen [this message]
2009-02-25 19:28 ` Greg KH
2009-02-26 10:30   ` Alex Buell
2009-02-28 12:49   ` Stefan Richter

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=20090226144856.GA23246@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=alex.buell@munted.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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

all inboxes | Powered by JetHome®