linux-kernel - Re: [PATCH 00/31] *** SUBJECT HERE ***

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:	Tue, 10 Mar 2009 18:46:24 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Scott James Remnant <scott@...onical.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 00/31] *** SUBJECT HERE ***

On Tue, 10 Mar 2009 16:23:48 +0000, Scott James Remnant wrote:
> module-init-tools on most distributions ships with a file that contains a
> large list of aliases to auto-load modules on demand, either by matching
> a MODALIAS string from the kernel uevent, or by the {block,char}-major-*
> aliases requested by the kernel when device nodes are opened.
> 
> There are convenient macros for defining these inside the kernel modules
> themselves, so they are exported by file2alias and put into the files
> created by depmod.  This is far preferable to a file in another package
> that has to be parsed every time modprobe is called (many, many times
> on a typical boot) and may get out of date.

I don't get how it could make any difference in terms of performance.
As far as I know, all the module aliases that come from the kernel are
assembled into /lib/modules/$version/modules.alias when the kernel is
installed, and that file must be processed by modprobe the exact same
way another configuration file would. Or am I missing something?

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