linux-kernel - Re: swsusp status report

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: <20060725151145.GG14964@redhat.com>
Date:	Tue, 25 Jul 2006 11:11:45 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	LKML <linux-kernel@...r.kernel.org>, Linux PM <linux-pm@...l.org>,
	Pavel Machek <pavel@....cz>
Subject: Re: swsusp status report

On Tue, Jul 25, 2006 at 01:25:14PM +0200, Rafael J. Wysocki wrote:

 > V. Freeing memory
 > 
 > Step (3) of the suspend procedure is completed by calling the same
 > functions that are normally used by kswapd, but in a slightly different way.
 > The part of swsusp responsible for that is referred to as 'the memory
 > shrinker' and it may sometimes be called by the suspend-to-RAM code as well

This isn't actually necessary though is it ?
(Ie, it's a bug that needs fixing?)

Good write-up btw, it may even be a nice addition to Documentation/power/  ?

		Dave

-- 
http://www.codemonkey.org.uk
-
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/