From: Stefan Rompf <stefan@loplof.de>
To: Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC] userland swsusp
Date: Wed, 16 Nov 2005 17:00:27 +0100
User-Agent: KMail/1.8
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200511161700.27239.stefan@loplof.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 989
Lines: 22

Pavel Machek wrote:

> This is prototype of userland swsusp. I'd like kernel parts to go in,
> probably for 2.6.16. Now, I'm not sure about the interface, ioctls are
> slightly ugly, OTOH it would be probably overkill to introduce
> syscalls just for this. (I'll need to add an ioctl for freeing memory
> in future).

I'm curious on the restrictions the userspace part would have to accept.
Can /usr/swsusp.c write to a file? Currently, you allow it, but I doubt
whether it would be wise to write to a file after you've snapshotted
kernel's filesystem state. OTOH, I don't want to reserve a partition just
for the image. Can userspace allocate memory after ioctl(SYS_FREEZE)?

I have userspace supported encryption of the image in mind.

Stefan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/