linux-kernel - Re: A workaround for request_firmware() stuck in module

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]

Message-ID: <20120906001804.645c243c@pyramind.ukuu.org.uk>
Date:	Thu, 6 Sep 2012 00:18:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Ming Lei <ming.lei@...onical.com>, Takashi Iwai <tiwai@...e.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Kay Sievers <kay@...y.org>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: A workaround for request_firmware() stuck in module_init

> But then you have cases where probe() -> register_with_my_subsystem() ->
> open(). Network devices come to mind. IE. udev must be able to deal with
> a synchronous firmware load from probe I'm afraid.

I don't believe so. You have

	begin probe
		find match .. .firmware_name is set
		issue firmware load request
		set defer flag
	end probe

Later..

	firmware load complete
	kick probe up arse

	begin probe
		find match .. .firmware is loaded
		call ->probe()
		register
		open
		happiness
	end probe

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