linux-kernel - Re: [PATCH 1/1] USBHID: remove setup mutex

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]

Message-ID: <alpine.LNX.1.10.0811231204150.19853@jikos.suse.cz>
Date:	Sun, 23 Nov 2008 12:05:01 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jiri Slaby <jirislaby@...il.com>
cc:	stern@...land.harvard.edu, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] USBHID: remove setup mutex

On Sat, 22 Nov 2008, Jiri Slaby wrote:

> It causes recursive locking warning and is unneeded after
> introduction of STARTED flag.
> 
> * Resume vs. stop is effectively solved by DISCONNECT flag.
> * No problem in suspend vs. start -- urb is submitted even after open
>   which is possible after connect which is called after start.
> * Resume vs. start solved by STARTED flag.
> * Suspend vs. stop -- no problem in killing urb and timer twice.

Yes, this was exactly point of my original question, thanks a lot for 
doublechecking. Applied.

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
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/