linux-kernel - MODULE_FIRMWARE() for fallback ucode files?

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: <s5hvasn47sk.wl-tiwai@suse.de>
Date:   Mon, 06 Feb 2017 17:12:59 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Johannes Berg <johannes.berg@...el.com>,
        Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
        Luca Coelho <luciano.coelho@...el.com>,
        Intel Linux Wireless <linuxwifi@...el.com>
Cc:     linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: MODULE_FIRMWARE() for fallback ucode files?

Hi,

currently iwlwifi driver lists only the latest firmware files in
MODULE_FIRMWARE() although the driver may read other older files.
And this confuses the openSUSE installer, since the installation image
is created based on the module information and copies only the
firmwares listed there.  A bug report is found at:
  https://bugzilla.suse.com/show_bug.cgi?id=1021082

Would it be better to list up all firmware files?  Or how can we
inform user-space which firmware files would be possibly loaded?

In anyway, the current situation is messy.  The driver declares the
firmware files that don't exist in the common linux-firmware git
tree.  If we list up only the latest API version, we should guarantee
that these files are landed in the official tree before upstreaming.

thanks,

Takashi