linux-kernel - [PATCH v3 0/4] Add request_firmware

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

Message-Id: <1384257736-3647-1-git-send-email-tiwai@suse.de>
Date:	Tue, 12 Nov 2013 13:02:12 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Prarit Bhargava <prarit@...hat.com>,
	Ming Lei <ming.lei@...onical.com>,
	Borislav Petkov <bp@...e.de>, x86@...nel.org,
	amd64-microcode@...64.org, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/4] Add request_firmware_direct() for microcode loader

Hi,

this is a revised patch series to introduce request_firmware_direct()
helper for avoiding the lengthy udev issue on microcode loader.
The original problem was stated in Prarit's post:
   https://lkml.org/lkml/2013/10/28/221

In short, microcode loader probes non-existing firmware files (which
are cases with every new chip), and each probe takes 60 seconds,
resulting in too long time until completed.

This solution is simply avoiding the udev fallback in
request_firmware() explicitly for drivers like microcode.

Of course, this doesn't mean to throw away further optimizations like
Prarit's patch.  It can be implemented in parallel with this.

 [PATCH v3 1/4] firmware: Introduce request_firmware_direct()
 [PATCH v3 2/4] microcode: Use request_firmware_direct()
 [PATCH v3 3/4] firmware: Use bit flags instead of boolean combos
 [PATCH v3 4/4] firmware: Suppress fallback warnings when CONFIG_FW_LOADER_USER_HELPER=n

v1->v2: Rebased on linux-next, add a fix for a bogus warning message
v2->v3: Convert to bit flags, fix warning message differently

Greg, could you take these patches through your driver tree, as
most of fixes are about the firmware loader itself.

thanks,

Takashi

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