| 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: <4C58D2AF.2070306@tuxonice.net> Date: Wed, 04 Aug 2010 12:38:39 +1000 From: Nigel Cunningham <nigel@...onice.net> To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> CC: Bojan Smojver <bojan@...ursive.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH]: Compress hibernation image with LZO (in-kernel) Hi. On 04/08/10 12:24, KAMEZAWA Hiroyuki wrote: > On Wed, 04 Aug 2010 12:24:57 +1000 > Nigel Cunningham<nigel@...onice.net> wrote: > >> Yes, because what's being written is the snapshot that was created in >> hibernation_snapshot. Any memory you allocate afterwards is irrelevant >> because it's not part of that snapshot that was made earlier and is now >> being written to disk. Think of the point where hibernation_snapshot is >> called as being like taking a photo, and this later part as like >> printing the photo. Once you've taken the photo, people in the photo can >> move around without making any difference to the photo you've taken. So >> here. Our vmallocs and so on after the snapshot don't affect it. >> > > I see. I misunderstood swsusp_save(). > Sorry for tons of noises. No problem at all! You learn how it works and I get to make sure I do understand how it works! :) Nigel -- 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