| 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: Fri, 29 Jul 2011 22:27:54 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Pavel Machek <pavel@....cz> Cc: Oliver Neukum <oneukum@...e.de>, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [linux-pm] better oopsing when frozen On Friday, July 29, 2011, Pavel Machek wrote: > On Mon 2011-07-25 10:43:19, Oliver Neukum wrote: > > Hi Rafael, > > > > I had a problem with the kernel stopping the machine forever because I got an > > oops while tasks were frozen. It seems to me that we should thaw when this > > happens. How about this approach? > > Danger, Will Robinson. You must not write to the filesystems after > hibernation started. By thawing, you may do just that. > > It should be safe to thaw as long as final suspend signature is not > on disk and will not be written there. This only applies to hibernation and only when we're going to restore from the image the presumably hasn't been saved yet, right? However, there's another problem I didn't think of before. Namely, we cannot thaw tasks before resuming devices in case we've already suspended them, because that will defeat the very purpose of the freezing in the first place. Thanks, Rafael -- 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