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:	Sun, 27 May 2007 21:20:03 +0000
From:	Pavel Machek <pavel@....cz>
To:	Bill Davidsen <davidsen@....com>
Cc:	David Greaves <david@...eaves.com>,
	Linux Kernel M/L <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?

Hi!

> >It is very dangerous to attempt a resume with a 
> >different kernel than the one
> >that has gone to sleep.
> >Different kernels may be compiled with different 
> >options that affect where or
> >how in-memory structures are saved.
> >
> If the mainline resume is depending on that no wonder 
> resume is so fragile. User action can change order of 
> module loads, kmalloc calls move allocated structures, 
> etc. Counting on anything to be locked in place seems 
> naive.

Look at code before spreading FUD. (suspend and suspend2 are same in
this matter).

							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 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/