Thread (73 messages) 73 messages, 7 authors, 2021-02-22

Re: [PATCH v17 08/10] PM: hibernate: disable when there are active secretmem users

From: Dan Williams <hidden>
Date: 2021-02-22 19:22:24
Also in: linux-arch, linux-arm-kernel, linux-fsdevel, linux-kselftest, linux-mm, linux-riscv, lkml, nvdimm

On Mon, Feb 22, 2021 at 2:24 AM Mike Rapoport [off-list ref] wrote:
On Mon, Feb 22, 2021 at 07:34:52AM +0000, Matthew Garrett wrote:
quoted
On Mon, Feb 08, 2021 at 10:49:18AM +0200, Mike Rapoport wrote:
quoted
It is unsafe to allow saving of secretmem areas to the hibernation
snapshot as they would be visible after the resume and this essentially
will defeat the purpose of secret memory mappings.
Sorry for being a bit late to this - from the point of view of running
processes (and even the kernel once resume is complete), hibernation is
effectively equivalent to suspend to RAM. Why do they need to be handled
differently here?
Hibernation leaves a copy of the data on the disk which we want to prevent.
Why not document that users should use data at rest protection
mechanisms for their hibernation device? Just because secretmem can't
assert its disclosure guarantee does not mean the hibernation device
is untrustworthy.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help