user/sven/linux.git/drivers/base/firmware_class.c, branch v2.6.14.7

[PATCH] drivers/base/*: use kzalloc instead of kmalloc+memset

2005-09-13T15:22:27Z

Fixes a bunch of memset bugs too. Signed-off-by: Lion Vollnhals Signed-off-by: Jiri Slaby Cc: Greg KH Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] modified firmware_class.c to support no hotplug

2005-09-07T23:57:26Z

Upgrade the request_firmware_nowait function to not start the hotplug action on a firmware update. This patch is tested along with dell_rbu driver on i386 and x86-64 systems. Signed-off-by: Abhay Salunke Cc: Greg KH Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] request_firmware(): avoid race conditions

2005-06-29T04:20:30Z

Avoid race occurs when some process have open file descriptor for class device attributes and already firmware allocated memory are freed. Don't allow negative loading timeout. Signed-off-by: Stanislaw W. Gruszka Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] add TIMEOUT to firmware_class hotplug event

2005-04-19T04:57:31Z

On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > The current implementation of the firmware class breaks a fundamental > assumption in udevd: that the physical device can be initialised fully > prior to executing the next event for that device. Here we add a TIMEOUT value to the hotplug environment of the firmware requesting event. I will adapt udevd not to wait for anything else, if it finds a TIMEOUT key. Signed-off-by: Kay Sievers Signed-off-by: Greg Kroah-Hartman

[PATCH] fix unnecessary increment in firmware_class_hotplug() and USB core

2004-11-29T02:40:36Z

> This patch is to fix unnecessary increment of 'i' used to > specify an element of an arry 'envp[]' in firmware_class_hotplug(). > The 'i' is already incremented in add_hotplug_env_var(), actually. you are right. The incrementation is wrong, but it doesn't have any negative effect. However the same applies for the usb_hotplug() function in drivers/usb/core/usb.c. Signed-off-by: Keiichiro Tokunaga Signed-off-by: Marcel Holtmann Signed-off-by: Greg Kroah-Hartman

[PATCH] Use add_hotplug_env_var() in firmware loader

2004-11-07T12:10:32Z

The add_hotplug_env_var() function is available and so use it in the firmware class code. Signed-off-by: Marcel Holtmann Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] unexport firmware_class

2004-10-28T01:30:48Z

it's marked static already, and there's no point in exporting it Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] firmware_class: avoid double free

2004-10-20T01:35:07Z

The error exit path in request_firmware frees the allocated struct firmware *firmware, which is good. What is not so good is that the value of firmware has already been copied out to the caller as *firmware_p. The risk is that the caller will pass this to release_firmware, a double free. This is exactly what will happen if the caller copied the example code if(request_firmware(&fw_entry, $FIRMWARE, device) == 0) copy_fw_to_device(fw_entry->data, fw_entry->size); release(fw_entry); from the firmware documentation. Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

merge

2004-10-19T01:03:51Z

[PATCH] security issue in firmware system

2004-10-18T01:22:09Z

The firmware loader has a security issue. Firmware on some devices can write to all memory through DMA. Therefore the ability to feed firmware to the kernel is equivalent to writing to /dev/kmem. CAP_SYS_RAWIO is needed to protect itself. [ Editors note: the firmware file is 0644, and owned by root, so this "security issue" is really only an issue for people who use capabilities explicitly, rather than the regular Unix permissions. This patch makes it do the same checks we do for /dev/mem etc. ] Signed-Off-By: Oliver Neukum Signed-off-by: Andrew Morton Signed-off-by: Adrian Bunk Signed-off-by: Linus Torvalds