| 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: <200707041010.11221.oliver@neukum.org> Date: Wed, 4 Jul 2007 10:10:10 +0200 From: Oliver Neukum <oliver@...kum.org> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: Miklos Szeredi <miklos@...redi.hu>, rjw@...k.pl, mjg59@...f.ucam.org, linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org, pavel@....cz, nigel@...el.suspend2.net Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway Am Mittwoch, 4. Juli 2007 schrieb Benjamin Herrenschmidt: > > > > > > Nope, something's wrong in fuse. You must be able to deal with sync > > > > > > until every task is frozen. > > > > > > > > > > Pipe dream > > > > > > > > Then tell me how you want to avoid that condition. > > > > > > Don't freeze :-) > > > > Then you will have to deal with all syscalls unfrozen tasks can make. > > Yup, and the majority of them is totally harmless. Looks like people > around here have a problem with the idea of writing robust drivers ... The majority is meaningless here. The subsystem works or works not. Reliably failing to work is better than working most of the time. What I am having a problem with is the rest of the system changing its behavior and expecting the drivers to cope with that out of the blue. 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