linux-kernel - Re: Issue with iwlwifi Firmware Loading When Compiled into the Kernel

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: <7100cb98b8e46793cfb1197c3af0f151a9628c9d.camel@sipsolutions.net>
Date: Thu, 31 Oct 2024 09:06:49 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Gang Yan <gang_yan@...mail.com>, Miri Korenblit
	 <miriam.rachel.korenblit@...el.com>, Kalle Valo <kvalo@...nel.org>
Cc: linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Issue with iwlwifi Firmware Loading When Compiled into the
 Kernel

> 
> To address this issue, I have considered two potential solutions:
> 
> 1、Modify the Driver Code: Implement a mechanism, such as delayed_work, to 
> give iwlwifi another chance to load the firmware after the filesystem has 
> been mounted. This would involve adding additional logic to the driver to 
> handle retries for firmware loading.
> 
> 2、Modify the Kconfig: Change the configuration to allow iwlwifi to be 
> compiled only as a module [CONFIG_IWLWIFI=m]. This way, the module can be 
> loaded after the filesystem is fully mounted, ensuring that the firmware
>  can be found and loaded successfully.

Neither of those is going to happen - you should just build the firmware
into the kernel (or initramfs might be enough?) if you want it built-in.
Or set up firmware loading userspace, and set it up appropriately to
only respond after / is mounted.

In any case, not a kernel problem. You need to fix it on your userspace.

johannes