From: Radek Pilar <mrkva@mrkva.eu>
To: linux-kernel@vger.kernel.org
Subject: Suspend to RAM - freeze & sync
Date: Fri, 18 Jan 2013 16:16:22 +0100 [thread overview]
Message-ID: <50F96746.1080304@mrkva.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Hello,
I'm trying to implement feature that removes cryptsetup keys from RAM on
suspend to RAM: mounts ramfs, unpacks initramfs to ramfs, moves /proc
/dev and /sys to ramfs, chroots, calls luksSuspend, suspends system
using /sys/power/state, after resume calls luksResume and cleans up.
However, there is a small issue I wasn't able to solve: after calling
luksSuspend, all attempts to access suspended device blocks - so most
likely some processes won't be able to freeze. The same issue will be
with sync just before suspend - if there are some data to be written,
sync() blocks. If I comment out freeze and sync from the suspend code,
it suspends (and wakes up) just fine - however, that patch will never be
accepted.
Is there any *correct* way to do this? (Skip freeze/sync on demand)?
Thanks
Radek Pilar
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next reply other threads:[~2013-01-18 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 15:16 Radek Pilar [this message]
2013-10-08 14:47 ` Pavel Machek
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=50F96746.1080304@mrkva.eu \
--to=mrkva@mrkva.eu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®