The driver does not check if mapping dma memory succeed.
The patch adds the checks and failure handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov <khoroshi...@ispras.ru>
---
drivers/net/wireless/admtek/adm8211.
On 26.03.2016 03:00, Till Kamppeter wrote:
On 03/25/2016 08:56 PM, Till Kamppeter wrote:
I am taking care of the 5 OpenPrinting proposals, please take care of
all the others, mark with IGNORE what you for sure do not want to mentor
and mark with a star what you want to mentor and also click
I do not see any reason to call usb_put_dev() if at76_load_internal_fw()
succeed.
But it is here from the very beginning. Any suggestions?
--
Thank you,
Alexey
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More
There is no need in usb_put_dev() if at76_load_internal_fw() succeed.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov <khoroshi...@ispras.ru>
---
drivers/net/wireless/atmel/at76c50x-usb.c | 2 --
1 file changed, 2 deletions(-)
diff
ipw2100_alloc_skb() and ipw2100_tx_send_data() do not check if mapping
dma memory succeed. The patch adds the checks and failure handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov <khoroshi...@ispras.ru>
---
drivers/net/wireless/i
prism54 checks for dma mapping errors by comparison returned address
with zero, while pci_dma_mapping_error() should be used.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov <khoroshi...@ispras.ru>
---
drivers/net/wireless/prism54/islpci
If hif_read_reg() or hif_write_reg() fail in wilc_wlan_cleanup(),
it calls release_bus() and continues execution. But it leads to double
release_bus() call that means double unlock of g_linux_wlan->hif_cs mutex.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Ale
If hif_read_reg() or hif_write_reg() fail in wilc_wlan_cleanup(),
it calls release_bus() and continues execution. But it leads to double
release_bus() call that means double unlock of g_linux_wlan->hif_cs mutex.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Ale
Reviewed-by: Alexey Khoroshilov khoroshi...@ispras.ru with small
suggestion. If we restore kmemdup() call, we have to handle ENOMEM
situations:
fw = kmemdup(fw_entry-data, fw_entry-size, GFP_KERNEL);
if (!fw)
return -ENOMEM;
On 27.07.2015 12:43, Mike Looijmans
On 24.07.2015 18:02, Mike Looijmans wrote:
On 24-07-15 10:39, Alexey Khoroshilov wrote:
Dear Mike,
On 24.07.2015 14:01, Mike Looijmans wrote:
Regarding this commit:
https://lkml.org/lkml/2014/12/12/709
rsi: fix memory leak in rsi_load_ta_instructions()
Memory allocated
On 24.07.2015 21:12, Kalle Valo wrote:
Mike Looijmans mike.looijm...@topic.nl writes:
On 24-07-15 13:35, Alexey Khoroshilov wrote:
On 24.07.2015 18:02, Mike Looijmans wrote:
On 24-07-15 10:39, Alexey Khoroshilov wrote:
Dear Mike,
On 24.07.2015 14:01, Mike Looijmans wrote:
Regarding
Memory allocated by kmemdup() in rsi_load_ta_instructions() is leaked.
But duplication of firmware data here is useless,
so the patch removes kmemdup() at all.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov khoroshi...@ispras.ru
---
drivers/net
(linuxtesting.org).
Signed-off-by: Alexey Khoroshilov khoroshi...@ispras.ru
---
drivers/net/wireless/ath/ath6kl/usb.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/net/wireless/ath/ath6kl/usb.c
b/drivers/net/wireless/ath/ath6kl/usb.c
index a6a5e40b3e98..9da3594fd010 100644
13 matches
Mail list logo
