linux-kernel - Re: Suspend to RAM

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 8 Oct 2013 16:47:04 +0200
From:	Pavel Machek <pavel@....cz>
To:	Radek Pilar <mrkva@...va.eu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Suspend to RAM - freeze & sync

Hi!
> 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)?

Maybe uswsusp interface is powerful enough to do this?
									Pavel


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/