Thread (12 messages) 12 messages, 3 authors, 2015-12-09

Re: [PATCH 2/4] test: firmware_class: add asynchronous request trigger

flat view

From: Kees Cook <hidden>
Date: 2015-12-09 21:09:09
Also in: lkml

On Tue, Dec 8, 2015 at 6:38 PM, Brian Norris
[off-list ref] wrote:
We might want to test for bugs like that found in commit f9692b2699bd
("firmware: fix possible use after free on name on asynchronous
request"), where the asynchronous request API had race conditions.

Let's add a simple file that will launch the async request, then wait
until it's complete and report the status. It's not a true async test
(we're using a mutex + wait_for_completion(), so we can't get more than
one going at the same time), but it does help make sure the basic API is
sane, and it can catch some class of bugs.
Awesome! This is great to add. Notes below...
quoted hunk ↗ jump to hunk
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Luis R. Rodriguez <redacted>
---
 lib/test_firmware.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 65 insertions(+)
diff --git a/lib/test_firmware.c b/lib/test_firmware.c
index 841191061816..ba0a12d0301d 100644
--- a/lib/test_firmware.c
+++ b/lib/test_firmware.c
@@ -12,6 +12,7 @@
 #include <linux/init.h>
 #include <linux/module.h>
 #include <linux/printk.h>
+#include <linux/completion.h>
 #include <linux/firmware.h>
 #include <linux/device.h>
 #include <linux/fs.h>
@@ -81,6 +82,57 @@ out:
 }
 static DEVICE_ATTR_WO(trigger_request);

+static DECLARE_COMPLETION(async_fw_done);
+
+static void trigger_async_request_cb(const struct firmware *fw, void *context)
+{
+       test_firmware = fw;
+       complete(&async_fw_done);
+}
+
+static ssize_t trigger_async_request_store(struct device *dev,
+                                          struct device_attribute *attr,
+                                          const char *buf, size_t count)
+{
+       int rc;
+       char *name;
+
+       name = kzalloc(count + 1, GFP_KERNEL);
+       if (!name)
+               return -ENOSPC;
+       memcpy(name, buf, count);
It strikes me that this (and the existing code) should use kstrndup
instead, since the request_firmware* interfaces will ignore \0 bytes
in the name:

    name = kstrndup(buf, count, GFP_KERNEL);
    if (!name)
        return -ENOSPC;
quoted hunk ↗ jump to hunk
+
+       pr_info("loading '%s'\n", name);
+
+       mutex_lock(&test_fw_mutex);
+       release_firmware(test_firmware);
+       test_firmware = NULL;
+       rc = request_firmware_nowait(THIS_MODULE, 1, name, dev, GFP_KERNEL,
+                                    NULL, trigger_async_request_cb);
+       /* Free 'name' ASAP, to test for race conditions */
+       kfree(name);
+       if (rc) {
+               pr_info("async load of '%s' failed: %d\n", name, rc);
Well, that's a little TOO soon. :) The pr_info uses it still.
quoted hunk ↗ jump to hunk
+               goto out;
+       }
+
+       wait_for_completion(&async_fw_done);
+
+       if (test_firmware) {
+               pr_info("loaded: %zu\n", test_firmware->size);
+               rc = count;
+       } else {
+               pr_err("failed to async load firmware\n");
+               rc = -ENODEV;
+       }
+
+out:
+       mutex_unlock(&test_fw_mutex);
+
+       return rc;
+}
+static DEVICE_ATTR_WO(trigger_async_request);
+
 static int __init test_firmware_init(void)
 {
        int rc;
@@ -97,9 +149,20 @@ static int __init test_firmware_init(void)
                goto dereg;
        }

+       rc = device_create_file(test_fw_misc_device.this_device,
+                               &dev_attr_trigger_async_request);
+       if (rc) {
+               pr_err("could not create async sysfs interface: %d\n", rc);
+               goto remove_file;
+       }
+
        pr_warn("interface ready\n");

        return 0;
+
+remove_file:
+       device_remove_file(test_fw_misc_device.this_device,
+                          &dev_attr_trigger_async_request);
 dereg:
        misc_deregister(&test_fw_misc_device);
        return rc;
@@ -111,6 +174,8 @@ static void __exit test_firmware_exit(void)
 {
        release_firmware(test_firmware);
        device_remove_file(test_fw_misc_device.this_device,
+                          &dev_attr_trigger_async_request);
+       device_remove_file(test_fw_misc_device.this_device,
                           &dev_attr_trigger_request);
        misc_deregister(&test_fw_misc_device);
        pr_warn("removed interface\n");
--
2.6.0.rc2.230.g3dd15c0
-Kees

-- 
Kees Cook
Chrome OS & Brillo Security
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help