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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/