From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: bbpetkov@yahoo.de
Cc: Pavel Machek <pavel@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] swap image signature check upon resume
Date: Sun, 9 Dec 2007 15:32:27 +0100 [thread overview]
Message-ID: <200712091532.28417.rjw@sisk.pl> (raw)
In-Reply-To: <200712091527.57523.rjw@sisk.pl>
On Sunday, 9 of December 2007, Rafael J. Wysocki wrote:
> On Sunday, 9 of December 2007, Borislav Petkov wrote:
> > On Sat, Dec 08, 2007 at 11:50:33PM +0100, Rafael J. Wysocki wrote:
> > > On Saturday, 8 of December 2007, Borislav Petkov wrote:
> > > > On Fri, Dec 07, 2007 at 09:19:09PM +0100, Rafael J. Wysocki wrote:
> > > >
> > > > ...
> > > >
> > > > > > > Well, there's a patchset in the current mainline that allows you to use
> > > > > > > arbitrary (sufficiently new) kernel to load the image and then restore the
> > > > > > > image kernel. So, you can hibernate 2.6.24-rc3 and use 2.6.24-rc2 to restore
> > > > > > > it, for example.
> > > > > > >
> > > > > > > I'm going to do that for i386 too.
> > > > > > right, this is d307c4a8e826c44f9633bd3f7e60d0491e7d885a (Hibernation: Arbitrary
> > > > > > boot kernel support - generic code), i should've seen that. What's the status of
> > > > > > those bits, from a quick scan it seems they need some rewiring (Kconfig, e.g.
> > > > > > CONFIG_ARCH_HIBERNATION_HEADER etc..) and arch-specific save and restore
> > > > > > functions?
> > > > >
> > > > > No, this code is fully functional. :-)
> > > > >
> > > > > The arch save and restore functions are in arch/x86/kernel/suspend_64.c .
> > > > >
> > > > > As I said, i386 is not yet supported.
> > > >
> > > > nice, holler if you need a tester when you have some prototypes ready. By the way,
> > > > what do you do when the suspend image header mismatches and it is unsafe to continue booting?
> > >
> > > If the image header doesn't match, we don't load it and return an error code,
> > > which usually results in the boot kernel continuing to boot.
> >
> > But if you continue to boot the filesystems were still mounted and fsck has to
> > go over them and check for errors. In the case of ext2 this takes relatively
> > long depending on the size of the partition. However, this is only the
> > smaller problem, the problem of data loss is what worries me.
>
> The filesystems are synced before the hibernation, so there shouldn't be data
> any loss.
s/data any loss/any data loss/ (sorry).
next prev parent reply other threads:[~2007-12-09 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 21:13 Borislav Petkov
2007-12-06 21:46 ` Rafael J. Wysocki
2007-12-07 7:12 ` Borislav Petkov
2007-12-07 20:19 ` Rafael J. Wysocki
2007-12-08 11:33 ` Borislav Petkov
2007-12-08 22:50 ` Rafael J. Wysocki
2007-12-09 6:55 ` Borislav Petkov
2007-12-09 14:27 ` Rafael J. Wysocki
2007-12-09 14:32 ` Rafael J. Wysocki [this message]
2007-12-09 16:09 ` Borislav Petkov
2007-12-09 21:46 ` Rafael J. Wysocki
2007-12-10 4:51 ` Borislav Petkov
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=200712091532.28417.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bbpetkov@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®