All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>,
	rusty@rustcorp.com.au, Linus Torvalds <torvalds@transmeta.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [2.5 patch] MODULE_FORCE_UNLOAD must depend on MODULE_UNLOAD
Date: Wed, 8 Jan 2003 00:07:42 +0100	[thread overview]
Message-ID: <20030107230742.GO6626@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301011435300.27623-100000@dell>

On Wed, Jan 01, 2003 at 02:55:01PM -0500, Robert P. J. Day wrote:

>...
> Loadable module support
>     
>     Does "Module unloading" mean whether or not I can run "rmmod"?
>   And if I deselect this, why can I still select "Forced module
>   unloading"?  Either I can unload or I can't, no?
>...

Thanks for spotting this, after reading kernel/module.c it seems obvious 
to me that you are right. The following simple patch fixes it:

--- linux-2.5.54/init/Kconfig.old	2003-01-08 00:05:12.000000000 +0100
+++ linux-2.5.54/init/Kconfig	2003-01-08 00:05:38.000000000 +0100
@@ -127,7 +127,7 @@
 
 config MODULE_FORCE_UNLOAD
 	bool "Forced module unloading"
-	depends on MODULES && EXPERIMENTAL
+	depends on MODULE_UNLOAD && EXPERIMENTAL
 	help
 	  This option allows you to force a module to unload, even if the
 	  kernel believes it is unsafe: the kernel will remove the module


> rday

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2003-01-07 22:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 19:55 observations on 2.5 config screens Robert P. J. Day
2003-01-01 20:07 ` Tomas Szepe
2003-01-01 20:15   ` Robert P. J. Day
2003-01-01 20:26   ` John Bradford
2003-01-02  1:55   ` Randy.Dunlap
2003-01-02  2:32     ` Robert P. J. Day
2003-01-02  4:10       ` Randy.Dunlap
2003-01-02  2:54     ` Tomas Szepe
2003-01-07 23:07 ` Adrian Bunk [this message]
2003-01-08 12:05   ` [2.5 patch] MODULE_FORCE_UNLOAD must depend on MODULE_UNLOAD Rusty Russell
2003-01-07 23:30 ` observations on 2.5 config screens Adrian Bunk
2003-01-07 23:42   ` Robert Love
2003-01-08  0:14     ` Russell King
2003-01-08 14:32     ` Bill Davidsen
2003-01-08 15:53       ` Robert Love
2003-01-08 18:36         ` Bill Davidsen
2003-01-08 19:50           ` Dave Jones
2003-01-08 22:49             ` Bill Davidsen
2003-01-09 12:50               ` Dave Jones
2003-01-09 16:12                 ` Bill Davidsen
2003-01-09 13:38             ` Ruslan U. Zakirov

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=20030107230742.GO6626@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.com \
    /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.