linux-kernel - Re: Unused modules in 2.6.x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Feb 2009 21:40:02 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	Alex Buell <alex.buell@...ted.org.uk>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Unused modules in 2.6.x

Alex Buell wrote:
> Hi,
> 
> Perhaps I missed something when the 2.6.x kernels got started a few
> years back, but why is it not possible for unused modules to be
> automatically unloaded anymore i.e with rmmod -a? I remember being able
> to do that with the 2.2.x and 2.4.x series a long time ago.

It's a pure userspace question now.  Well, almost, except of the
single bit which were kept before 2.6  for each module - if it
was loaded with -k flag (auto-unload) or not.

Better question to ask, IMHO, is why network drivers don't gets
referenced properly as all other drivers are.  Because right now
they're unused even if the network interfaces are up-n-running,
and rmmod'ing a seemingly unused module will cause that particular
interface to be removed too...

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/