| 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
| ||
|
Message-Id: <200707041208.40735.oliver@neukum.org> Date: Wed, 4 Jul 2007 12:08:40 +0200 From: Oliver Neukum <oliver@...kum.org> To: Paul Mackerras <paulus@...ba.org> Cc: linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, Matthew Garrett <mjg59@...f.ucam.org> Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway Am Mittwoch, 4. Juli 2007 schrieb Paul Mackerras: > Oliver Neukum writes: > > > > It's not lost, it's sitting in RAM, and will be sent out when you > > > resume. > > > > Unfortunately this is not the case. The URB will error out. > > So the higher-level driver needs to do the sensible thing, i.e., > resubmit the URB after resume. It's not rocket science. The data is > not lost, it's sitting in RAM, and the higher-level driver will send > it out when you resume. If not, then we fix the higher-level driver. You cannot simply restart the URB without thinking. The device after resumption may or may not be in the stage you left it. It needs to be rechecked and some settings must be renewed. You cannot simple throw an URB from an arbitrary stage of the protocol at it. Suspension of devices can only happen at some points in the protocol. Oliver - 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