linux-kernel - RE: [PATCH] mei: fix mismatch in mutex unlock-lock in mei_amthif

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-prev] [day] [month] [year] [list]

Date:	Sun, 23 Dec 2012 09:22:19 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Alexey Khoroshilov <khoroshilov@...ras.ru>,
	"Greg KH (gregkh@...uxfoundation.org)" <gregkh@...uxfoundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ldv-project@...uxtesting.org" <ldv-project@...uxtesting.org>
Subject: RE: [PATCH] mei: fix mismatch in mutex unlock-lock in
 mei_amthif_read()



> 
> Users of mei_amthif_read() expect it leaves dev->device_lock held, while
> there is a path where mei_amthif_read() unlocks device_lock and returns -
> ERESTARTSYS.
> 
> The patch move code locking device_lock back before the return.
> 
> Found by Linux Driver Verification project (linuxtesting.org).
> 
> Signed-off-by: Alexey Khoroshilov <khoroshilov@...ras.ru>
Acked-by:   Tomas Winkler <tomas.winkler@...el.com>

Greg.  This should be eligible for 3.8.

Thanks
Tomas


--
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/