linux-kernel - Re: dlopen-like facility for conditional loading of symbols in modules (Re: Firmware for new ti_usb_3410

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:	Sat, 03 Mar 2007 18:51:51 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Oleg Verych <olecom@...wer.upol.cz>
CC:	Oliver Neukum <oliver@...kum.org>,
	linux-usb-devel@...ts.sourceforge.net, Greg KH <greg@...ah.com>,
	Dale Martenson <dmartenson@...titech.com>,
	Al Borchers <alborchers@...inerpoint.com>,
	LKML <linux-kernel@...r.kernel.org>, mit-devel@...ts.printk.net
Subject: Re: dlopen-like facility for conditional loading of symbols in modules
 (Re: Firmware for new ti_usb_3410_5052 devices)

Oleg Verych wrote:
> 
> Maybe modules' dlopen() like facility would be better to handle static
> firmware or any other on-demand static data like ID tables etc.?
> 
> I.e. some additional flag for an exported symbol (in a module), that
> this symbol maybe dynamically requested and used. As far as i can see,
> depmod generates static map, unresolved symbols must be in the kernel
> (System.map).
> 

You can do this with request_module() and having your module overwrite a 
hook.

> It will solve problem of having multiple unneeded firmware images if
> driver handles many devices and firmware is allowed to be in the
> kernel. No need in additional secure infrastructure.
> 

This seems like a hacky way to accomplish what request_firmware() does 
clearer!

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