linux-kernel - Re: [2.6.21.1] resume doesn't run suspended kernel?

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 May 2007 19:57:38 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Bill Davidsen <davidsen@....com>,
	Linux Kernel M/L <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?

On Monday, 28 May 2007 15:26, Pavel Machek wrote:
> Hi!
> 
> > >That's clear, I'll have to use xen or kvm or similar which restores 
> > >the system as suspended. Thanks for the clarification of the limitations.
> > >
> > Sorry, I wrote that late at night and quickly. I should have said 
> > "design decision" rather than "limitation," For systems which don't do 
> > multiple kernels it's not an issue.
> > 
> > I certainly would not have made the same decision, but I didn't write 
> > the code. It seems more robust to save everything than to try to 
> > identify what has and hasn't changed in a modular kernel.
> 
> We rely on atomic copy routine not moving inside the kernel. Yes, it
> would be possible to copy it to "known good" address and gain ability
> to resume different kernels. Actually it should not be _that_ hard.

Yup.  Don't we do something like this for the (ACPI-based) suspend to RAM
already?

Greetings,
Rafael
-
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/