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:	Wed, 23 Jul 2008 09:38:21 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:	Henrik Rydberg <rydberg@...omail.se>,
	<linux-input@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	<robfitz@...k.net>, <akpm@...l.org>, Jiri Kosina <jikos@...os.cz>,
	<vojtech@...e.cz>, <dmonakhov@...nvz.org>,
	<johannes@...solutions.net>, Oliver Neukum <oliver@...kum.org>
Subject: Re: [PATCH] linux-input: bcm5974-0.57: mode-switch to atp_open,
 cleanup bug fixed

On Tue, 22 Jul 2008, Dmitry Torokhov wrote:

> > 4. From the state (!opened,suspended), calling open fails. Where are we?
> >
> 
> Manual suspend will surely cause open to fail. Autosuspend - if
> autoresume fails then (closed, unknown) otherwise (closed,
> autosuspended - autosuspension may not kick in immediately I think).
> 
> > 5. From the state (opened,suspended), calling resume fails. What state
> > are we in?
> > 
> 
> Screwed up ;) From the driver POV still (opened, suspended) I think.

In both of these cases, the final result depends on the reason why the
resume failed.  If it failed for administrative reasons (such as it was
an autoresume and the device had been manually suspended), then the
final state is still suspended.  But if it fails because the kernel
actually tried to resume the device and couldn't do so, then the final
state is that the device is gone, logically disconnected.

Alan Stern

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ