| 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: Mon, 23 Jul 2007 16:01:07 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Miklos Szeredi <miklos@...redi.hu>, stern@...land.harvard.edu Cc: oliver@...kum.org, nigel@...el.suspend2.net, nigel@...pend2.net, jbms@....edu, miltonm@....com, ying.huang@...el.com, linux-kernel@...r.kernel.org, david@...g.hm, linux-pm@...ts.linux-foundation.org Subject: Re: [linux-pm] Re: Hibernation considerations On Monday, 23 July 2007 15:08, Miklos Szeredi wrote: > > > > The reason is that we want them to "park" in safe places, ie. where there > > > > are no locks held etc. Thus, these safe places need to be chosen somehow > > > > and since they are not marked throughout the code, we choose the obvious > > > > one. :-) > > > > > > Why shouldn't locks be held? > > > > > > No locks which are required for suspend must be held, sure. But > > > otherwise holding locks doesn't matter at all. > > > > If you can provide a way to tell them apart, this would work. > > Without some marking we can't tell obviously. > > Are there many such locks? We can easily check by adding some > debugging code to the lock primitives, to make them yell if they are > used during suspend. This way we can only obtain information from systems that use hibernation quite often. Alan has recently proposed to introduce "suspend locks" to be acquired during a suspend/hibernation and such that we can leave uninterruptible tasks that don't hold any of them. Unfortunately, I have no link to his original message at hand. 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