linux-kernel - Re: Problems loading firmware using built-in drivers with kernels that use initramfs.

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:	Thu, 3 Sep 2015 10:33:51 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	"Luis R. Rodriguez" <mcgrof@...e.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ming Lei <ming.lei@...onical.com>,
	Takashi Iwai <tiwai@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
	"Jie, Yang" <yang.jie@...el.com>,
	"joonas.lahtinen@...ux.intel.com" <joonas.lahtinen@...ux.intel.com>,
	Al Viro <viro@...iv.linux.org.uk>, Kay Sievers <kay@...y.org>,
	David Woodhouse <dwmw2@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	yalin wang <yalin.wang2010@...il.com>,
	Tom Gundersen <teg@...m.no>
Subject: Re: Problems loading firmware using built-in drivers with kernels
 that use initramfs.

On Thu, Sep 3, 2015 at 10:23 AM, Arend van Spriel <arend@...adcom.com> wrote:
> On 09/03/2015 01:46 AM, Luis R. Rodriguez wrote:
>>
>> On Wed, Sep 2, 2015 at 4:29 PM, Dmitry Torokhov
>> <dmitry.torokhov@...il.com> wrote:
>>>
>>> On Wed, Sep 2, 2015 at 4:22 PM, Luis R. Rodriguez <mcgrof@...e.com>
>>> wrote:
>>>> IMHO its just as hacky as using -EPROBE_DEFER too, but its at least
>>>> preemptively hacky. Sadly I can't think of clear and clever way for the
>>>> kernel
>>>> to know when firmware will be ready either...  Would userspace know?
>>>> Should the
>>>> kernel learn this from userspace ?
>>>
>>>
>>> Yes. Given only userspace knows when firmware is available (I could
>>> have it on a separate device and mount it at some time). So maybe
>>> userpsace should simply try and scan busses for unbound devices and
>>> tell them to re-probe when it decides that firmware is finally
>>> available.
>>
>>
>> OK, the folks wanting this mechanism can implement it then. Short of
>> that we only have hacks.
>
>
> So what does "userspace knows when firmware is available" mean here. The
> specific firmware file the driver wants or the collection of firmware files
> which may or may not have the specific firmware file the driver wants. I
> assume the latter and re-probe will fail as expected.

Right, the latter.

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