firmware: Be a bit more verbose about direct firmware loading failure
PATCH 1/1 firmware: Be a bit more verbose about direct firmware loading failure
The direct firmware loading interface is a bit quiet about failures. Failures that occur during loading are masked if firmware exists in multiple locations, and may be masked entirely in the event that we fall back to the user mode helper code. It would be nice to see some of the more unexpected errors get logged, so in the event that you expect the direct firmware loader to work (like if CONFIG_FW_LOADER_USER_HELPER is enabled), and something goes wrong, you can figure out what happened.
--- drivers/base/firmware_class.c | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-)
drivers/base/firmware_class.c +25 -13
@@ -282,31 +282,35 @@ static noinline_for_stack long fw_file_size(struct file *file)return st.size; } -static bool fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) +static int fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) {long size;char *buf; +int rc; size =fw_file_size (file);if (size <=0 ) -return false; +return -EINVAL ; buf =vmalloc (size);if (!buf) -return false; -if (kernel_read (file,0 , buf, size) != size) { +return -ENOMEM ; + rc =kernel_read (file,0 , buf, size); +if (rc != size) { +if (rc >0 ) + rc = -EIO ;vfree (buf); -return false; +return rc; } fw_buf->data = buf; fw_buf->size = size; -return true; +return 0 ; } -static bool fw_get_filesystem_firmware (struct device *device, +static int fw_get_filesystem_firmware (struct device *device,struct firmware_buf *buf) {int i; -bool success = false; +int rc = -ENOENT ;char *path =__getname ();for (i =0 ; i <ARRAY_SIZE (fw_path); i++) {
@@ -321,14 +325,17 @@ static bool fw_get_filesystem_firmware(struct device *device, file =filp_open (path,O_RDONLY ,0 );if (IS_ERR (file))continue ; - success =fw_read_file_contents (file, buf); + rc =fw_read_file_contents (file, buf);fput (file); -if (success) +if (rc) +dev_warn (device,"firmware, attempted to load %s, but failed with error %d\n" , + path, rc); +else break ; }__putname (path); -if (success) { +if (!rc) {dev_dbg (device,"firmware: direct-loading firmware %s\n" , buf->fw_id);mutex_lock (&fw_lock);
@@ -337,7 +344,7 @@ static bool fw_get_filesystem_firmware(struct device *device,mutex_unlock (&fw_lock); } -return success; +return rc; }/* firmware holds the ownership of pages */
@@ -1086,9 +1093,14 @@ _request_firmware(const struct firmware **firmware_p, const char *name, } } -if (!fw_get_filesystem_firmware (device, fw->priv)) + ret =fw_get_filesystem_firmware (device, fw->priv); +if (ret) { +dev_warn (device,"Direct firmware load failed with error %d\n" , + ret); +dev_warn (device,"Falling back to user helper\n" ); ret =fw_load_from_user_helper (fw, name, device, uevent, nowait, timeout); + }/* don't cache firmware handled without uevent */ if (!ret)
Signature · 1 line
1.8.1.4
Quoted 1 line · Neil Horman
The direct firmware loading interface is a bit quiet about failures. Failures
Because there are several pre-defined search paths, and generally the requested firmware only exists in one of these paths.
Quoted 2 lines
that occur during loading are masked if firmware exists in multiple locations, and may be masked entirely in the event that we fall back to the user mode
You still can figure out the request falls back to user mode loading since we have the "firmware: direct-loading firmware %s" log.
Quoted 1 line
helper code. It would be nice to see some of the more unexpected errors get
What are the unexpected errors?
Quoted 3 lines
logged, so in the event that you expect the direct firmware loader to work (like if
CONFIG_FW_LOADER_USER_HELPERis enabled), and something goes wrong, you can figure out what happened.
Looks we didn't meet this case, do you have real examples?
Quoted 57 lines
Signed-off-by Neil Horman <[email protected]>CC Ming Lei <[email protected]>CC Greg Kroah-Hartman <[email protected]>--- drivers/base/firmware_class.c | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-)drivers/base/firmware_class.c +12
-8@@ -282,31 +282,35 @@ static noinline_for_stack long fw_file_size(struct file *file)return st.size; } -static bool fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) +static int fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) {long size;char *buf; +int rc; size =fw_file_size (file);if (size <=0 ) -return false; +return -EINVAL ; buf =vmalloc (size);if (!buf) -return false; -if (kernel_read (file,0 , buf, size) != size) { +return -ENOMEM ; + rc =kernel_read (file,0 , buf, size); +if (rc != size) { +if (rc >0 ) + rc = -EIO ;vfree (buf); -return false; +return rc; } fw_buf->data = buf; fw_buf->size = size; -return true; +return 0 ; } -static bool fw_get_filesystem_firmware (struct device *device, +static int fw_get_filesystem_firmware (struct device *device,struct firmware_buf *buf) {int i; -bool success = false; +int rc = -ENOENT ;char *path =__getname ();for (i =0 ; i <ARRAY_SIZE (fw_path); i++) {
drivers/base/firmware_class.c static bool fw_get_filesystem_firmware(struct device *device, · line 332
Quoted 10 lines
drivers/base/firmware_class.c +4
-2@@ -321,14 +325,17 @@ static bool fw_get_filesystem_firmware(struct device *device, file =filp_open (path,O_RDONLY ,0 );if (IS_ERR (file))continue ; - success =fw_read_file_contents (file, buf); + rc =fw_read_file_contents (file, buf);fput (file); -if (success) +if (rc) +dev_warn (device,"firmware, attempted to load %s, but failed with error %d\n" , + path, rc);
The above may introduce noises.
Quoted 20 lines
drivers/base/firmware_class.c +3
-2+else break ; }__putname (path); -if (success) { +if (!rc) {dev_dbg (device,"firmware: direct-loading firmware %s\n" , buf->fw_id);mutex_lock (&fw_lock);@@ -337,7 +344,7 @@ static bool fw_get_filesystem_firmware(struct device *device,mutex_unlock (&fw_lock); } -return success; +return rc; }/* firmware holds the ownership of pages */
drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1100
Quoted 9 lines
drivers/base/firmware_class.c +5
-1@@ -1086,9 +1093,14 @@ _request_firmware(const struct firmware **firmware_p, const char *name, } } -if (!fw_get_filesystem_firmware (device, fw->priv)) + ret =fw_get_filesystem_firmware (device, fw->priv); +if (ret) { +dev_warn (device,"Direct firmware load failed with error %d\n" , + ret); +dev_warn (device,"Falling back to user helper\n" );
You should merge the two warnings to into one?
drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1106
Quoted 6 lines
drivers/base/firmware_class.c +1
-0ret =fw_load_from_user_helper (fw, name, device, uevent, nowait, timeout); + }/* don't cache firmware handled without uevent */ if (!ret)
Thanks,
--
Ming Lei
Quoted 6 lines · Ming Lei
Quoted 1 line · Neil Horman
The direct firmware loading interface is a bit quiet about failures. Failures
Because there are several pre-defined search paths, and generally the requested firmware only exists in one of these paths.
This is true, but you'll note this patch doesn't make any noise in the event that a firmware isn't found until all the search paths are exhausted. I didn't consider this "unexpected".
Quoted 6 lines
Quoted 2 lines
that occur during loading are masked if firmware exists in multiple locations, and may be masked entirely in the event that we fall back to the user mode
You still can figure out the request falls back to user mode loading since we have the "firmware: direct-loading firmware %s" log.
Yes, but you're looking at it backwards, that only prints out if the direct load works. If it doesn't, you get silence, which is bad.
Quoted 4 lines
Quoted 1 line
helper code. It would be nice to see some of the more unexpected errors get
What are the unexpected errors?
If you get a short read in the direct load path for example, or if someone mounts an nfs share over the firmware search path and you get an ESTALE. Alternatively, if the vmalloc fails during the direct load path, these would be "unexpected" errors
Quoted 6 lines
Quoted 3 lines
logged, so in the event that you expect the direct firmware loader to work (like if
CONFIG_FW_LOADER_USER_HELPERis enabled), and something goes wrong, you can figure out what happened.Looks we didn't meet this case, do you have real examples?
Yeah, we had a vmalloc failure in the direct load path, and unknowingly had forgot to configure CONFIG_FW_LOADER_USER_HELPER, so the module load failed with an ENOENT, even though the firmware was clearly present on the filesystem. This patch helped us track that down.
Neil
Quoted 114 lines
Quoted 57 lines
Signed-off-by Neil Horman <[email protected]>CC Ming Lei <[email protected]>CC Greg Kroah-Hartman <[email protected]>--- drivers/base/firmware_class.c | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-)drivers/base/firmware_class.c +12
-8@@ -282,31 +282,35 @@ static noinline_for_stack long fw_file_size(struct file *file)return st.size; } -static bool fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) +static int fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) {long size;char *buf; +int rc; size =fw_file_size (file);if (size <=0 ) -return false; +return -EINVAL ; buf =vmalloc (size);if (!buf) -return false; -if (kernel_read (file,0 , buf, size) != size) { +return -ENOMEM ; + rc =kernel_read (file,0 , buf, size); +if (rc != size) { +if (rc >0 ) + rc = -EIO ;vfree (buf); -return false; +return rc; } fw_buf->data = buf; fw_buf->size = size; -return true; +return 0 ; } -static bool fw_get_filesystem_firmware (struct device *device, +static int fw_get_filesystem_firmware (struct device *device,struct firmware_buf *buf) {int i; -bool success = false; +int rc = -ENOENT ;char *path =__getname ();for (i =0 ; i <ARRAY_SIZE (fw_path); i++) {drivers/base/firmware_class.c static bool fw_get_filesystem_firmware(struct device *device, · line 332
Quoted 10 lines
drivers/base/firmware_class.c +4
-2@@ -321,14 +325,17 @@ static bool fw_get_filesystem_firmware(struct device *device, file =filp_open (path,O_RDONLY ,0 );if (IS_ERR (file))continue ; - success =fw_read_file_contents (file, buf); + rc =fw_read_file_contents (file, buf);fput (file); -if (success) +if (rc) +dev_warn (device,"firmware, attempted to load %s, but failed with error %d\n" , + path, rc);The above may introduce noises.
Quoted 20 lines
drivers/base/firmware_class.c +3
-2+else break ; }__putname (path); -if (success) { +if (!rc) {dev_dbg (device,"firmware: direct-loading firmware %s\n" , buf->fw_id);mutex_lock (&fw_lock);@@ -337,7 +344,7 @@ static bool fw_get_filesystem_firmware(struct device *device,mutex_unlock (&fw_lock); } -return success; +return rc; }/* firmware holds the ownership of pages */ drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1100
Quoted 9 lines
drivers/base/firmware_class.c +5
-1@@ -1086,9 +1093,14 @@ _request_firmware(const struct firmware **firmware_p, const char *name, } } -if (!fw_get_filesystem_firmware (device, fw->priv)) + ret =fw_get_filesystem_firmware (device, fw->priv); +if (ret) { +dev_warn (device,"Direct firmware load failed with error %d\n" , + ret); +dev_warn (device,"Falling back to user helper\n" );You should merge the two warnings to into one?
drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1106
Quoted 6 lines
drivers/base/firmware_class.c +1
-0ret =fw_load_from_user_helper (fw, name, device, uevent, nowait, timeout); + }/* don't cache firmware handled without uevent */ if (!ret)Thanks,
--
Ming Lei
Quoted 10 lines · Neil Horman
Quoted 6 lines · Ming Lei
Quoted 1 line · Neil Horman
The direct firmware loading interface is a bit quiet about failures. Failures
Because there are several pre-defined search paths, and generally the requested firmware only exists in one of these paths.
This is true, but you'll note this patch doesn't make any noise in the event that a firmware isn't found until all the search paths are exhausted. I didn't consider this "unexpected".
Yes, it will cause noise, suppose the firmware is in the last search path, and we may always get the warning during the first three searches, and it is certainly
annoying, isn't it?
Quoted 9 lines
Quoted 7 lines
Quoted 3 lines
that occur during loading are masked if firmware exists in multiple locations, and may be masked entirely in the event that we fall back to the user mode
You still can figure out the request falls back to user mode loading since we have the "firmware: direct-loading firmware %s" log.
Yes, but you're looking at it backwards, that only prints out if the direct load works. If it doesn't, you get silence, which is bad.
OK, you can change to only log the failure.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
helper code. It would be nice to see some of the more unexpected errors get
What are the unexpected errors?
If you get a short read in the direct load path for example, or if someone mounts an nfs share over the firmware search path and you get an ESTALE.
That is easy to find, and no one should mount one fs on firmware path.
Quoted 2 lines
Alternatively, if the vmalloc fails during the direct load path, these would be "unexpected" errors
This one might make sense since size of some firmwares may be several mega bytes, and vmalloc space is a bit limited on 32bit arch, so how about just log this failure in fw_read_file_contents()?
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
logged, so in the event that you expect the direct firmware loader to work (like if
CONFIG_FW_LOADER_USER_HELPERis enabled), and something goes wrong, you can figure out what happened.Looks we didn't meet this case, do you have real examples?
Yeah, we had a vmalloc failure in the direct load path, and unknowingly had forgot to configure
CONFIG_FW_LOADER_USER_HELPER, so the module load failed with an ENOENT, even though the firmware was clearly present on the filesystem. This patch helped us track that down.
Fair enough, looks it is helpful to add some log, :-)
Quoted 122 lines
Neil
Quoted 106 lines
Quoted 57 lines
Signed-off-by Neil Horman <[email protected]>CC Ming Lei <[email protected]>CC Greg Kroah-Hartman <[email protected]>--- drivers/base/firmware_class.c | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-)drivers/base/firmware_class.c +12
-8@@ -282,31 +282,35 @@ static noinline_for_stack long fw_file_size(struct file *file)return st.size; } -static bool fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) +static int fw_read_file_contents (struct file *file,struct firmware_buf *fw_buf) {long size;char *buf; +int rc; size =fw_file_size (file);if (size <=0 ) -return false; +return -EINVAL ; buf =vmalloc (size);if (!buf) -return false; -if (kernel_read (file,0 , buf, size) != size) { +return -ENOMEM ; + rc =kernel_read (file,0 , buf, size); +if (rc != size) { +if (rc >0 ) + rc = -EIO ;vfree (buf); -return false; +return rc; } fw_buf->data = buf; fw_buf->size = size; -return true; +return 0 ; } -static bool fw_get_filesystem_firmware (struct device *device, +static int fw_get_filesystem_firmware (struct device *device,struct firmware_buf *buf) {int i; -bool success = false; +int rc = -ENOENT ;char *path =__getname ();for (i =0 ; i <ARRAY_SIZE (fw_path); i++) {drivers/base/firmware_class.c static bool fw_get_filesystem_firmware(struct device *device, · line 332
Quoted 10 lines
drivers/base/firmware_class.c +4
-2@@ -321,14 +325,17 @@ static bool fw_get_filesystem_firmware(struct device *device, file =filp_open (path,O_RDONLY ,0 );if (IS_ERR (file))continue ; - success =fw_read_file_contents (file, buf); + rc =fw_read_file_contents (file, buf);fput (file); -if (success) +if (rc) +dev_warn (device,"firmware, attempted to load %s, but failed with error %d\n" , + path, rc);The above may introduce noises.
Quoted 20 lines
drivers/base/firmware_class.c +3
-2+else break ; }__putname (path); -if (success) { +if (!rc) {dev_dbg (device,"firmware: direct-loading firmware %s\n" , buf->fw_id);mutex_lock (&fw_lock);@@ -337,7 +344,7 @@ static bool fw_get_filesystem_firmware(struct device *device,mutex_unlock (&fw_lock); } -return success; +return rc; }/* firmware holds the ownership of pages */ drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1100
Quoted 9 lines
drivers/base/firmware_class.c +5
-1@@ -1086,9 +1093,14 @@ _request_firmware(const struct firmware **firmware_p, const char *name, } } -if (!fw_get_filesystem_firmware (device, fw->priv)) + ret =fw_get_filesystem_firmware (device, fw->priv); +if (ret) { +dev_warn (device,"Direct firmware load failed with error %d\n" , + ret); +dev_warn (device,"Falling back to user helper\n" );You should merge the two warnings to into one?
Quoted 4 lines
drivers/base/firmware_class.c +1
-0ret =fw_load_from_user_helper (fw, name, device, uevent, nowait, timeout); + }Quoted 8 lines
drivers/base/firmware_class.c _request_firmware(const struct firmware **firmware_p, const char *name, · line 1106
Quoted 2 lines
drivers/base/firmware_class.c +0
-0/* don't cache firmware handled without uevent */ if (!ret)Thanks,
--
Ming Lei--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Ming Lei
Quoted 7 lines · Neil Horman
Quoted 6 lines · Ming Lei
Quoted 1 line · Neil Horman
The direct firmware loading interface is a bit quiet about failures. Failures
Because there are several pre-defined search paths, and generally the requested firmware only exists in one of these paths.
Quoted 9 lines
Quoted 3 lines
This is true, but you'll note this patch doesn't make any noise in the event that a firmware isn't found until all the search paths are exhausted. I didn't consider this "unexpected".
Yes, it will cause noise, suppose the firmware is in the last search path, and we may always get the warning during the first three searches, and it is certainly
annoying, isn't it?
Please re-read the patch, then point out to me which printk the above action will trigger, because its not happening in my testing. If you'll take a look at fw_get_filesystem_firmware, you'll see that if the filp_open on a firmware file fails, we continue the for loop through the list of available search paths. No error is generated in the case you describe above.
The exceptions to that rule are:
1) If no file is found in _any_ of the search paths, in which case fw_get_filesystem_firmware will return -ENOENT, causing _request_firmware to print "Direct firmware load failed with error -ENOENT. Falling back to user helper".
2) If a file is successfully opened by fw_get_filesystem_firmware, but something goes wrong during the read in fw_read_file_contents, we print "firmware attempted to load <file>, but failed with error <X>", followed by the printk from (1) indicating that we are falling back to the user mode helper path.
Both of these execptions should be rare, and are something the administrator will want to know about, so as not to confuse the real error with the mystery -ENOENT you would get if you fell back to the user mode helepr and it wansn't configured on in the running kernel.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
that occur during loading are masked if firmware exists in multiple locations, and may be masked entirely in the event that we fall back to the user mode
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
You still can figure out the request falls back to user mode loading since we have the "firmware: direct-loading firmware %s" log.
Yes, but you're looking at it backwards, that only prints out if the direct load works. If it doesn't, you get silence, which is bad.
OK, you can change to only log the failure.
That is exactly what this patch does.
Quoted 10 lines
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
helper code. It would be nice to see some of the more unexpected errors get
What are the unexpected errors?
If you get a short read in the direct load path for example, or if someone mounts an nfs share over the firmware search path and you get an ESTALE.
That is easy to find, and no one should mount one fs on firmware path.
Thats really rather the problem isn't it? this patch is an assertion that its not that easy to find the root cause of a firmware load problem currently, even if you haven't done something dumb, like mount a network FS on your firmware path. And I agree you shouldn't do such things, but that doesnt' mean that people won't or have good reason to try (I can certainly see mounting the firmware path on an NFS mount for embedded system development with limited storage). Regardless, when people do do something silly, we should tell them so, not mask the problem behind a mystery -ENOENT error.
Quoted 7 lines
Quoted 2 lines
Alternatively, if the vmalloc fails during the direct load path, these would be "unexpected" errors
This one might make sense since size of some firmwares may be several mega bytes, and vmalloc space is a bit limited on 32bit arch, so how about just log this failure in
fw_read_file_contents()?
It does exactly that, and a
little more. Why just catch the vmalloc error? What if kernel_read fails for some reason? I see no reason to catch the vmalloc error specifcally, when we can catch any error generated by direct read path (that doesn't include simple file not found errors for any single entry in the search path).
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
logged, so in the event that you expect the direct firmware loader to work (like if
CONFIG_FW_LOADER_USER_HELPERis enabled), and something goes wrong, you can figure out what happened.
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
Looks we didn't meet this case, do you have real examples?
Yeah, we had a vmalloc failure in the direct load path, and unknowingly had forgot to configure
CONFIG_FW_LOADER_USER_HELPER, so the module load failed with an ENOENT, even though the firmware was clearly present on the filesystem. This patch helped us track that down.Fair enough, looks it is helpful to add some log, :-)
Thanks :)
Neil
Ming Lei
Acked-byQuoted 6 lines · Neil Horman
Quoted 1 line
Please re-read the patch, then point out to me which printk the above action will trigger, because its not happening in my testing. If you'll take a look at
fw_get_filesystem_firmware, you'll see that if thefilp_openon a firmware file fails, we continue the for loop through the list of available search paths. No error is generated in the case you describe above.
You are right, sorry for missing "if (IS_ERR(file)) continue;", and looks the patch is good.
Thanks,
--
Ming Lei
Quoted 8 lines · Ming Lei
Quoted 6 lines · Neil Horman
Quoted 1 line
Please re-read the patch, then point out to me which printk the above action will trigger, because its not happening in my testing. If you'll take a look at
fw_get_filesystem_firmware, you'll see that if thefilp_openon a firmware file fails, we continue the for loop through the list of available search paths. No error is generated in the case you describe above.
Quoted 6 lines
You are right, sorry for missing "if (
IS_ERR(file)) continue;", and looks the patch is good.Acked-by Ming Lei <[email protected]>Thanks,
Awesome, thanks!
Neil
Quoted 3 lines
--
Ming Lei
Quoted 4 lines · Neil Horman
Both of these execptions should be rare, and are something the administrator will want to know about, so as not to confuse the real error with the mystery
-ENOENTyou would get if you fell back to the user mode helepr and it wansn't configured on in the running kernel.
Except, of course, for Intel processor microcode updates, which are going to cause ENOENT on a large number of systems.
This will generate a large number of questions by users on the distro MLs.
However, IMHO this is *not* a reason to refuse this patch series. If anything, at least for Debian I will use it as an opportunity to educate people about the existence of microcode update packages in "non-free".
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Quoted 6 lines · Henrique de Moraes Holschuh
Quoted 4 lines · Neil Horman
Both of these execptions should be rare, and are something the administrator will want to know about, so as not to confuse the real error with the mystery
-ENOENTyou would get if you fell back to the user mode helepr and it wansn't configured on in the running kernel.
Quoted 9 lines
Except, of course, for Intel processor microcode updates, which are going to cause ENOENT on a large number of systems.
This will generate a large number of questions by users on the distro MLs.
However, IMHO this is *not* a reason to refuse this patch series. If anything, at least for Debian I will use it as an opportunity to educate people about the existence of microcode update packages in "non-free".
I agree. If people are running with downlevel microcode, they shold know about it. You can't expect request_firmware to fail silently. If people complain, I think the right solution would be to add a test to the microcode_request_fw function to check for the existence of the file before requesting it.
Neil
Quoted 6 lines
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Quoted 12 lines · Neil Horman
Quoted 11 lines · Henrique de Moraes Holschuh
Quoted 4 lines · Neil Horman
Both of these execptions should be rare, and are something the administrator will want to know about, so as not to confuse the real error with the mystery
-ENOENTyou would get if you fell back to the user mode helepr and it wansn't configured on in the running kernel.Except, of course, for Intel processor microcode updates, which are going to cause ENOENT on a large number of systems.
This will generate a large number of questions by users on the distro MLs.
Quoted 8 lines
Quoted 4 lines
However, IMHO this is *not* a reason to refuse this patch series. If anything, at least for Debian I will use it as an opportunity to educate people about the existence of microcode update packages in "non-free".
I agree. If people are running with downlevel microcode, they shold know about it. You can't expect
request_firmwareto fail silently. If people complain, I think the right solution would be to add a test to themicrocode_request_fwfunction to check for the existence of the file before requesting it.
Make it a firmware loader API for "optional" firmware (i.e. which doesn't complain on ENOENT), leaving for the caller the detail of whether a firmware-not-there failure should be logged or not.
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Quoted 17 lines · Henrique de Moraes Holschuh
Quoted 16 lines · Neil Horman
Quoted 15 lines · Henrique de Moraes Holschuh
Quoted 4 lines · Neil Horman
Both of these execptions should be rare, and are something the administrator will want to know about, so as not to confuse the real error with the mystery
-ENOENTyou would get if you fell back to the user mode helepr and it wansn't configured on in the running kernel.Except, of course, for Intel processor microcode updates, which are going to cause ENOENT on a large number of systems.
This will generate a large number of questions by users on the distro MLs.
However, IMHO this is *not* a reason to refuse this patch series. If anything, at least for Debian I will use it as an opportunity to educate people about the existence of microcode update packages in "non-free".
Quoted 9 lines
Quoted 4 lines
I agree. If people are running with downlevel microcode, they shold know about it. You can't expect
request_firmwareto fail silently. If people complain, I think the right solution would be to add a test to themicrocode_request_fwfunction to check for the existence of the file before requesting it.Make it a firmware loader API for "optional" firmware (i.e. which doesn't complain on ENOENT), leaving for the caller the detail of whether a firmware-not-there failure should be logged or not.
That makes sense, I'll subit that in a separate patch this afternoon Thanks!
Neil
Quoted 6 lines
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh