mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Pi-Cheng Chen <pi-cheng.chen@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: cpufreq: mediatek: allow modular build
Date: Fri, 11 Sep 2015 11:13:41 +0100	[thread overview]
Message-ID: <20150911101341.GN21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150911100916.GO9650@linux>

On Fri, Sep 11, 2015 at 03:39:16PM +0530, Viresh Kumar wrote:
> On 11-09-15, 10:58, Russell King - ARM Linux wrote:
> > Not module "unplug" (I've never heard it called that before).  A module
> > with a module_init() but no module_exit() can only be added to a running
> > kernel, and never removed.  That's intentional behaviour.
> 
> Ah, I see. I wasn't sure that a module with no module_exit() can't be
> removed.

Yes, but it's not that simple.

A module with no module_init() and no module_exit() is what's called a
library module, which can be inserted, and later removed provided no
other module depends on anything the library module exports.

A module with a module_init() but no module_exit() is one which can be
inserted, but never removed.

A module with a module_init() and a module_exit() can be inserted, and
later removed in much the same way as the library module mentioned above.

See kernel/module.c:

        /* If it has an init func, it must have an exit func to unload */
        if (mod->init && !mod->exit) {
                forced = try_force_unload(flags);
                if (!forced) {
                        /* This module can't be removed */
                        ret = -EBUSY;
                        goto out;
                }
        }

and

        if (mod->init != NULL && mod->exit == NULL) {
                printed_something = 1;
                seq_puts(m, "[permanent],");
        }


-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-09-11 10:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  8:15 Arnd Bergmann
2015-09-11  8:17 ` Viresh Kumar
2015-09-11  8:22   ` Arnd Bergmann
2015-09-11  8:25     ` Viresh Kumar
2015-09-11  8:36       ` Arnd Bergmann
2015-09-11  8:38         ` Viresh Kumar
2015-09-11  9:34           ` Russell King - ARM Linux
2015-09-11  9:40             ` Viresh Kumar
2015-09-11  9:58               ` Russell King - ARM Linux
2015-09-11 10:09                 ` Viresh Kumar
2015-09-11 10:13                   ` Russell King - ARM Linux [this message]
2015-09-11 10:19                     ` Viresh Kumar

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=20150911101341.GN21084@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pi-cheng.chen@linaro.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=viresh.kumar@linaro.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

all inboxes | Powered by JetHome®