linux-kernel - Re: [PATCH] DMI-based module autoloading

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:	Mon, 7 May 2007 18:27:36 -0700
From:	Greg KH <gregkh@...e.de>
To:	Lennart Poettering <lennart@...ttering.net>
Cc:	linux-kernel@...r.kernel.org, kay.sievers@...y.org
Subject: Re: [PATCH] DMI-based module autoloading

On Tue, May 08, 2007 at 02:54:29AM +0200, Lennart Poettering wrote:
> To take advantage of DMI based module autoloading, a driver should
> export one or more MODULE_ALIAS fields similar to these:
> 
> MODULE_ALIAS("dmi:*:svnMICRO-STARINT'LCO.,LTD:pnMS-1013:pvr0131*:cvnMICRO-STARINT'LCO.,LTD:ct10:*");
> MODULE_ALIAS("dmi:*:svnMicro-StarInternational:pnMS-1058:pvr0581:rvnMSI:rnMS-1058:*:ct10:*");
> MODULE_ALIAS("dmi:*:svnMicro-StarInternational:pnMS-1412:*:rvnMSI:rnMS-1412:*:cvnMICRO-STARINT'LCO.,LTD:ct10:*");
> MODULE_ALIAS("dmi:*:svnNOTEBOOK:pnSAM2000:pvr0131*:cvnMICRO-STARINT'LCO.,LTD:ct10:*");

Is there any way to automatically generate these aliases (like we do for
PCI and USB), in a way that is easier for the developer, instead of
having to figure out how to create such a "wierd" string like these by
hand?

> These lines are specific to my msi-laptop.c driver. They are basically
> just a concatenation of a few carefully selected DMI fields with all
> potentially bad characters stripped.

What is a "bad character" here?

thanks,

greg k-h
-
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/