linux-kernel - Re: [PATCH] request_firmware: skip timeout if userspace was not notified

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, 04 Aug 2007 23:20:49 +0200
From:	Javier Pello <javier.pello@...c.es>
To:	david@...g.hm
CC:	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: [PATCH] request_firmware: skip timeout if userspace was not 
	notified

On Sat, 4 Aug 2007, David Lang wrote:
> what I've been told is that with the drive built-in instead of
> modular you can create a filesystem that has only the firmware
> on it, nothing else, and have the kernel find and load it (no
> userspace software involved)

I'm afraid my understanding of the kernel is not very deep, so
I don't know of this method you're describing.

Anyway, if there's no userspace involved then nothing should
change. The patch I sent only affects the behaviour of the kernel
when it actually tries to send a firmware request to userspace
(and it determines that the request was not received). If the
kernel loads a firmware image without userspace support, it must
do so in a codepath different from request_firmware, whose point
is precisely to send a firmware request and wait for it, and
request_firmware is the only function that effectively changes
with my patch.

Javier

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