[pkg-cryptsetup-devel] cryptsetup and hibernation

Christoph Anton Mitterer calestyo at scientia.org
Mon Mar 27 01:29:46 BST 2023


On Mon, 2023-03-27 at 02:21 +0200, Guilhem Moulin wrote:
> The resume script is supplied in src:initramfs-tools, and the stage
> at
> which it is run is AFAICT currently undocumented there, so we can't
> rely
> on it in src:cryptsetup documentation either (I don't see how it
> could
> be moved elsewhere, but it remains at the discretion of the
> initramfs-tools
> maintainers).

Well I didn't want to document the opening of cryptsetup device
relative to resume, but simply saying something like:

The devices necessary for the root filesystem, /usr, the resume swap
area and any device with the `initramfs` option in crypttab are first
tried to be mapped (as in opened or "decrypted") in initramfs-tools’s
local-top phase. Any which couldn't be mapped there are retried in
local-block.

Just to make it clear, where cryptsetup itself does that, and then
people can still have a look where resume (or whatever else they're
interested in) is currently loaded from.

Perhaps one should use swap device in the above text... I'd assume that
cryptsetup simply tries to make the RESUME= device available, and since
that is right now only swap devices (not files), I guess it doesn't try
to find out on which device a swap file would be located.


> Yeah, unless you can give a good reason to document that.

No, not really... just wondered if you wanted it, in case you'd have
asked me for a PR with documentation for the above.


Cheers,
Chris.



More information about the pkg-cryptsetup-devel mailing list