linux-kernel - Re: [PATCH]: Compress hibernation image with LZO (in-kernel)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100804112444.bc1a575f.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Wed, 4 Aug 2010 11:24:44 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Nigel Cunningham <nigel@...onice.net>
Cc:	Bojan Smojver <bojan@...ursive.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: Compress hibernation image with LZO (in-kernel)

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.

Thanks,
-Kame

--
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/