linux-kernel - Re: Suspend to disk: do we HAVE to use swap?

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 31 Oct 2006 07:16:39 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	John Richard Moser <nigelenki@...cast.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Suspend to disk:  do we HAVE to use swap?

On Tuesday, 31 October 2006 04:42, John Richard Moser wrote:
> Something dumb came into my head, and the question is thus brought up
> here:  Do we HAVE to use swap for suspend to disk? How about the file
> system?

In short, we could use regular files for the suspend in the same way in which we
use them for swap.  Namely, we could bmap() a file and create a map of it
(eg. with extents) that would be used for accessing the corresponding disk
sectors at the block device level.  Then, to be able to read the image the
resume code would have to be provided with the number of the sector in which
the suspend image header is located.

However, we already have code that allows us to use swap files for the suspend
and turning a regular file into a swap file is as easy as running 'mkswap' and
'swapon' on it.

Greetings,
Rafael

-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
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/