|
|
|
Re: unloading a module with no exit routine? | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Sun, 28 Jun 2009, Mulyadi Santosa wrote:
> On Sun, Jun 28, 2009 at 12:58 AM, Robert P. J. Day<rpjday@xxxxxxxxxxxxxx> wrote:
> >
> > as i read it, if you build and load a module with no exit() routine,
> > once that module's loaded, it is absolutely unloadable until you
> > reboot the system, is that correct? i just tested that and, via
> > lsmod, i see:
> >
> > $ lsmod
> > ...
> > hi 1760 0 [permanent]
> >
> > that certainly suggests to *me* that it's there for good, no matter
> > what i do. is that correct?
>
> what happen if you forcefully unload that "hi" module? let's put aside
> any memory leakage etc.... I guess the kernel has somewhat "generic"
> unload function.
"rmmod -f" has no effect. i may take a look at the source code for
rmmod, but i'm starting to think that that module is truly unloadable
at this point.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
[Newbies FAQ] [Kernel Development Development] [Site Home] [IETF Annouce] [Git] [Networking] [Security] [Bugtraq] [Rubini] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Networking] [Linux RAID] [Linux SCSI] [Linux ACPI] [DDR & Rambus] [UNIX Filesystems] [Linux Resources]
![]() |
![]() |