netdev - Re: calling request_firmware() from module init will not work with recent/future udev versions

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, 16 Jan 2012 13:05:19 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
	Tom Gundersen <teg@...m.no>, Andy Whitcroft <apw@...onical.com>
Subject: Re: calling request_firmware() from module init will not work with
 recent/future udev versions

On Mon, Jan 16, 2012 at 09:57, Johannes Berg <johannes@...solutions.net> wrote:
> On Sun, 2012-01-15 at 16:33 +0100, Kay Sievers wrote:

> Let's say you have iwlwifi, built into the kernel, and an
> initramfs that doesn't contain the iwlwifi firmware.
> What will happen (last I checked anyway) is this: iwlwifi will do an
> async firmware request, and the udev in initramfs will say "don't have
> it", thus unbinding and you have to sysfs bind or module reload.

Right, currently. if no firmware is found, udev will write "-1" to the
"loading" file in /sys, which will cancel the kernel's firmware
request.

> What I'm was asking then is this: Can udev know that it is running from
> initramfs (presumably that can't be too hard) and simply not reply to
> async requests it doesn't have firmware for? Then once the real root is
> mounted it could satisfy (or not) firmware requests from the real root.

We can surely change it to not cancel the firmware request.

Either by making it aware that we run from initramfs, or by never
cancelling any firmware request and just leave it hanging around for
forever?

We need to decide what's the best model here, if we want a timeout at
all, if yes, how large it should be, and if and when we should cancel
requests.

Kay
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html