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]
Message-ID: <87zlolzv15.fsf@basil.nowhere.org>
Date:	Sun, 13 Jul 2008 17:03:02 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next 00/11] remove CONFIG_KMOD

Johannes Berg <johannes@...solutions.net> writes:

> I've rebased this patch series against -next-20080708 (one conflict
> against ftrace, another against BKL pushdown) and fixed the things
> Adrian Bunk pointed out.

You forgot to say why you want to remove that?
 
I personally like to not set CONFIG_KMOD because the auto loader
tends to load way too many modules. e.g. currently when someone requests
aes on x86 you get three different aes modules (including VIA PadLock
aes and an unoptimized C version), and keeping those around
is just a waste. 

Also if I didn't load a driver I prefer if it's not loaded at all.
This is also useful for power saving for example where it's better
to keep modules not loaded that you don't need and it's hard to
control who accesses the respective devices.

Please keep the option.

Thanks.

-Andi

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ