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: <1280890070.2741.11.camel@shrek.rexursive.com>
Date:	Wed, 04 Aug 2010 12:47:50 +1000
From:	Bojan Smojver <bojan@...ursive.com>
To:	Nigel Cunningham <nigel@...onice.net>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: Compress hibernation image with LZO (in-kernel)

On Wed, 2010-08-04 at 12:42 +1000, Nigel Cunningham wrote:
> Is it  standalone? I'm not seeing the relationship between the two
> parts at the moment. 

Once the compression/decompression gets applied, then it can be a
standalone patch, because sync_read is no longer used (we need the data
_now_ in order to decompress it, so async read would not give us much).

I already have it split on my box, so once I finalize, that's how I'll
send.

Points taken for all the other comments. Thank you.

PS. Right now, I'm seeing segfaults on resume with my
overlapping/in-place approach. So, I'll have to find out what is going
on first.

-- 
Bojan

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