From: Domenico Andreoli <cavok@debian.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Linux PM <linux-pm@vger.kernel.org>,
954061@bugs.debian.org
Subject: Re: [PATCH 0/2] Preparing to phase out uswsusp
Date: Sun, 3 May 2020 13:19:08 +0200 [thread overview]
Message-ID: <20200503111908.GA8066@dumbo> (raw)
In-Reply-To: <CAJZ5v0g4GyaxtKvbdS7u0rWtMbd075hPzFO-+Cz0q+zM1WbE-g@mail.gmail.com>
On Wed, Apr 29, 2020 at 01:06:01PM +0200, Rafael J. Wysocki wrote:
> On Mon, Apr 27, 2020 at 11:53 AM Domenico Andreoli
> <domenico.andreoli@linux.com> wrote:
> >
> > On Sun, Apr 26, 2020 at 05:46:37PM +0200, Rafael J. Wysocki wrote:
> > > On Monday, April 13, 2020 9:08:43 PM CEST Domenico Andreoli wrote:
> > > > Dear maintainers,
> > > >
> > > > it is my understanding that the usermode software suspend is not any
> > > > more the first choice for suspend/hibernate needs (uswsusp tool did
> > > > not receive any update in years).
> > >
> > > While the last part is true, the user space utilities are still usable.
> > >
> >
> > Indeed I've been using them until now and work perfectly.
> >
> > > Moreover, the kernel-based hibernation is still missing one important
> > > piece with respect to the user space variant, which is image encryption.
> > >
> >
> > Interesting, is it advertised anywhere?
>
> I'm not sure what you mean by "advertised".
Wrong and misinformed wording, encryption is also mentioned on uswsusp
web page http://suspend.sourceforge.net/.
>
> There is a way to combine hibernation with dm-crypt which is kind of
> described by Documentation/power/swsusp-dmcrypt.rst, but the lack of
> encryption support in the built-in hibernation code is not documented
> otherwise AFAICS.
I use a full disk encryption on Debian, swap included. I've to say
that everything works flawlessly, after the pass phrase is entered it
resumes from hibernation whatever system I used to hibernate: it works
either with uswsusp or in-kernel mechanism.
Is there any advantage in the approach of swsusp-dmcrypt.rst?
Thanks,
Domenico
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
prev parent reply other threads:[~2020-05-03 11:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 19:08 [PATCH 0/2] Preparing to phase out uswsusp Domenico Andreoli
2020-04-13 19:08 ` [PATCH 1/2] uswsusp: use enter/leave helpers and make a global variable static Domenico Andreoli
2020-04-26 16:11 ` Rafael J. Wysocki
2020-04-13 19:08 ` [PATCH 2/2] uswsusp: build only when configured Domenico Andreoli
2020-04-25 11:47 ` [uswsusp] 08e6583083: stress-ng.futex.ops_per_sec -11.4% regression kernel test robot
2020-04-26 16:16 ` [PATCH 2/2] uswsusp: build only when configured Rafael J. Wysocki
2020-04-27 9:48 ` Domenico Andreoli
2020-04-29 11:20 ` Rafael J. Wysocki
2020-05-01 7:10 ` Domenico Andreoli
2020-05-01 14:54 ` Rafael J. Wysocki
2020-05-03 13:31 ` Domenico Andreoli
2020-05-03 17:25 ` Domenico Andreoli
2020-04-26 15:46 ` [PATCH 0/2] Preparing to phase out uswsusp Rafael J. Wysocki
2020-04-27 9:53 ` Domenico Andreoli
2020-04-29 11:06 ` Rafael J. Wysocki
2020-05-03 11:19 ` Domenico Andreoli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200503111908.GA8066@dumbo \
--to=cavok@debian.org \
--cc=954061@bugs.debian.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.