From: Borislav Petkov <bbpetkov@yahoo.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] swap image signature check upon resume
Date: Fri, 7 Dec 2007 08:12:36 +0100 [thread overview]
Message-ID: <20071207071236.GB4923@gollum.tnic> (raw)
In-Reply-To: <200712062246.49422.rjw@sisk.pl>
On Thu, Dec 06, 2007 at 10:46:48PM +0100, Rafael J. Wysocki wrote:
> On Thursday, 6 of December 2007, Borislav Petkov wrote:
> > Hi Pavel,
> > hi Rafael,
> >
> > after a quick search i couldn't find anything dealing with the topic in the
> > subject line so here we go:
> >
> > One sometimes can mix up (and by one i mean me) the
> > kernel images one boots after having suspended the machine previously. There can
> > be at least two reasons for that:
> >
> > 1. too many kernels in grub and having forgotten with which i suspended.
> > 2. compile and install a new kernel and forget about it, suspend in the evening
> > and then boot with the new kernel;
> >
> > in both cases you end up staring at fsck since they filesystems haven't been unmounted,
> > of course. Or at least see the warning message of some journal recovery whisk away.
> >
> > In order to alleviate that, one could probably go, imho, and write in the swsusp_header
> > the kernel version which suspended the machine (UTS_RELEASE) alongside
> > SWSUSP_SIG and check that against the kernel version of the image just booting.
> > If they match then all is well, if not, one could
> >
> > a) issue a BIG FAT WARNING and reboot telling the user to select the proper
> > image
> > b) ask the user what to do:
> > - proceed as if "noresume" has been entered on the kernel command line
> > - reboot after issuing the kernel version which suspended the machine
> > -
> > c)...
> >
> > In case you guys think something like that might be of use i can come up with a
> > patch in the next coupla days...
>
> 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?
--
Regards/Gruß,
Boris.
next prev parent reply other threads:[~2007-12-07 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 21:13 [RFC] swap image signature check upon resume Borislav Petkov
2007-12-06 21:46 ` Rafael J. Wysocki
2007-12-07 7:12 ` Borislav Petkov [this message]
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
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=20071207071236.GB4923@gollum.tnic \
--to=bbpetkov@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).