[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110921235515.7476c5fe.lucasvr@gmail.com>
Date: Wed, 21 Sep 2011 23:55:15 -0300
From: "Lucas C. Villa Real" <lucasvr@...il.com>
To: linux-kernel@...r.kernel.org
Subject: [PATCH] Initialize pointer on request_firmware
Hello, folks,
I've seen some kernel oopses when suspending my machine. The problem comes from isight_firmware, which assumes that, on error, a call to request_firmware() will initialize the provided pointer to the firmware image to NULL.
The patch below fixes the isight_firmware side of the problem and also ensures that request_firmware() always sets the pointer to NULL on such cases (it currently does that for all except one situation).
Signed-off-by: Lucas C. Villa Real <lucasvr@...olinux.org>
--- linux-3.0.4/drivers/base/firmware_class.c.orig 2011-09-21 21:03:01.000000000 -0300
+++ linux-3.0.4/drivers/base/firmware_class.c 2011-09-21 21:03:13.000000000 -0300
@@ -523,6 +523,7 @@ static int _request_firmware(const struc
if (WARN_ON(usermodehelper_is_disabled())) {
dev_err(device, "firmware: %s will not be loaded\n", name);
+ *firmware_p = NULL;
return -EBUSY;
}
--- linux-3.0.4/drivers/usb/misc/isight_firmware.c.orig 2011-09-21 20:47:39.000000000 -0300
+++ linux-3.0.4/drivers/usb/misc/isight_firmware.c 2011-09-21 20:47:46.000000000 -0300
@@ -39,7 +39,7 @@ static int isight_firmware_load(struct u
{
struct usb_device *dev = interface_to_usbdev(intf);
int llen, len, req, ret = 0;
- const struct firmware *firmware;
+ const struct firmware *firmware = NULL;
unsigned char *buf = kmalloc(50, GFP_KERNEL);
unsigned char data[4];
const u8 *ptr;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists