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
| ||
|
Date: Thu, 5 Jul 2007 15:23:43 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Miklos Szeredi <miklos@...redi.hu> Cc: oliver@...kum.org, paulus@...ba.org, stern@...land.harvard.edu, johannes@...solutions.net, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, pavel@....cz, mjg59@...f.ucam.org, benh@...nel.crashing.org Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway On Thursday, 5 July 2007 13:54, Miklos Szeredi wrote: > > > Limiting what a userspace filesystem can do would defeat the whole > > > purpose of the bloody thing. This is not negotiable ;) > > > > Which doesn't change the fact that FUSE _is_ special, because it adds > > dependencies between processed that were not present before. > > OK, fuse is special. So is the userspace driver framework (UIO) > proposed by Greg KH and co. Now what can be done about these? > > - making them not-special is not an option due to the established > interfaces, which don't allow restartability. > > - fixing the freezer is pretty much impossible because the > dependencies between the tasks cannot be known. > > - removing the freezer and fixing the drivers seems workable, we > already have a prototype in the form of the powermac architecture. > > It seems pretty clear cut. Whining about how much problems this will > cause won't get us nearer to a solution. Yes, that's pretty clear cut, but we should start from fixing the drivers. :-) Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth - 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