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: <Pine.LNX.4.64.0708041007430.6905@asgard.lang.hm>
Date:	Sat, 4 Aug 2007 10:09:19 -0700 (PDT)
From:	david@...g.hm
To:	Javier Pello <javier.pello@...c.es>
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, Javier Pello wrote:

>> I've been told that it's possible to have the kernel pull the firmware
>> off of an initrd (or was it initramfs, I keep confusing the two) without
>> having any userspace, just put the right file in the right place
>> (unfortunantly I've never gotten around to testing this) will this patch
>> break this feature?
>
> Correct me if I'm wrong, but I understand that the way this works is having
> the initramfs become an "early userspace", a filesystem that is mounted,
> well, earlier during boot, so that it is available before drivers begin
> to initialise (earlier: as a rootfs_initcall, as opposed to at the end of
> the boot process), but that in all respects behaves as a fully-fledged root
> filesystem. In particular, firmware should be requested from userspace in
> the standard way, and the patch should not break anything. I would test
> this to be sure, but I have absolutely no experience preparing an initramfs.

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)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ