diff options
| author | Jesper Juhl | 2012-03-24 23:39:18 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2012-04-10 18:17:33 +0200 |
| commit | 401c90e56c48b1c642507a8bec91b7ae21f1156e (patch) | |
| tree | 8247bc25bf858747e62719a231e5a7eb9562031f /drivers/staging/vt6656/key.c | |
| parent | staging:iio:core add missing increment of loop index in iio_map_array_unregis... (diff) | |
| download | kernel-qcow2-linux-401c90e56c48b1c642507a8bec91b7ae21f1156e.tar.gz kernel-qcow2-linux-401c90e56c48b1c642507a8bec91b7ae21f1156e.tar.xz kernel-qcow2-linux-401c90e56c48b1c642507a8bec91b7ae21f1156e.zip | |
staging/media/as102: Don't call release_firmware() on uninitialized variable
If, in drivers/staging/media/as102/as102_fw.c::as102_fw_upload(), the call
cmd_buf = kzalloc(MAX_FW_PKT_SIZE, GFP_KERNEL);
should fail and return NULL so that we jump to the 'error:' label,
then we'll end up calling 'release_firmware(firmware);' with
'firmware' still uninitialized - not good.
The easy fix is to just initialize 'firmware' to NULL when we declare
it, since release_firmware() deals gracefully with being passed NULL
pointers.
Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/vt6656/key.c')
0 files changed, 0 insertions, 0 deletions