linux-kernel - [PATCH] firmware loader: allow disabling of udev as firmware loader

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>] [day] [month] [year] [list]

Message-ID: <8B2F6FFD0BD1E448853114367400A37306FCD2E026@BLRX7MCDC203.AMER.DELL.COM>
Date:	Mon, 9 Jun 2014 19:14:32 +0530
From:	<B_B_Singh@...L.com>
To:	<linux-kernel@...r.kernel.org>
CC:	<teg@...m.no>, <ming.lei@...onical.com>,
	<gregkh@...uxfoundation.org>, <Abhay_Salunke@...l.com>,
	<sr@...x.de>, <arnd@...db.de>, <kay@...y.org>,
	<Matt_Domsch@...l.com>, <Srinivas_G_Gowda@...l.com>,
	<Stuart_Hayes@...l.com>
Subject: [PATCH] firmware loader: allow disabling of udev as firmware loader

Hi All,

The existing BIOS-DUP's will not work on latest kernel, which has CONFIG_FW_LOADER_USER_HELPER=n  configured in Kernel config by default which is not expected by the dell_rbu.

We have made a changes in BIOS-Dell Update Package so that BIOS-DUP will pick the payload from the /lib/firmware/ path & update the BIOS even when CONFIG_FW_LOADER_USER_HELPER=n is configured .

We have tested this patch http://www.spinics.net/lists/kernel/msg1755247.html with latest BIOS Dell Update Package (which has new implementation for the BIOS update i.e, copying the BIOS payload in /lib/firmware path & dell_rbu picks the payload from the same path)  & with  stable upstream      kernel-3.14.5 & we don't see any negative effects/errors for dell_rbu.

All the Test results are positive.

Regards
Balaji Singh

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