linux-kernel - Staging: serqt_usb2: kmalloc(GFP_NOIO) with spinlock held in qt_break() and qt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 05 Aug 2011 18:35:10 +0400
From:	Alexey Khoroshilov <khoroshilov@...ras.ru>
To:	gregkh@...e.de
CC:	wfp5p@...ginia.edu, linux-kernel@...r.kernel.org
Subject: Staging: serqt_usb2: kmalloc(GFP_NOIO) with spinlock held in qt_break()
 and qt_tiocmset()

qt_break() calls usb_control_msg() with spinlock held,
while usb_control_msg() calls kmalloc(GFP_NOIO) and indirectly usb_alloc_urb(GFP_NOIO).

The same is true for qt_tiocmget() and qt_tiocmset().

Is replacing spinlock with mutex an appropriate solution to fix the issue?

Found by Linux Driver Verification project (linuxtesting.org).

--
Alexey Khoroshilov
Linux Verification Center, ISPRAS
--
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/