UH-OH, Self-followup:
On 2019-07-14 21:30, Ian Zimmerman wrote:
> I find it odd that there is apparently no central way to track which
> firmwares are being loaded without a debugging kernel.
>
> The relevant messages in linux/drivers/base/firmware_loader/main.c are
> all dev_dbg(), which as I understand does nothing on a non-debug kernel.
> Even the message printed when the firmware file is missing is of that
> type.
>
> I guess I could turn on the userspace helper, set it to some script that
> just logs every request and fails, and then remove the whole
> /lib/firmware tree, but that is a _really_ round-about way.
Solved with a kernel patch:
--- a/drivers/base/firmware_loader/main.c 2019-07-13 23:01:15.000000000
-0700
+++ b/drivers/base/firmware_loader/main.c 2019-07-14 23:33:22.348028910
-0700
@@ -336,7 +336,7 @@
path);
continue;
}
- dev_dbg(device, "direct-loading %s\n", fw_priv->fw_name);
+ pr_notice("direct-loading firmware %s\n", fw_priv->fw_name);
fw_priv->size = size;
fw_state_done(fw_priv);
break;
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
