Re: resuming swsusp twice

[Stefan Seyfried <seife@suse.de>]

Andy Isaacson wrote:

> Perhaps the image should be more rigorously checked?  I'm wishing that
> it would verify that the header and the image matched, after it finishes

in your case, the header and the image matched. There was no new image
on disk. And no new header.

> reading the image.  For example, computing the hash
> 
> MD5(header || image)     (|| denotes "concatenate" in crypto pseudocode.)
> 
> and storing that hash in a final trailing block.  Additionally, of
> course, as soon as the resume has read the image it should overwrite the
> header; and the header should include jiffies or something along those

the header is actually overwritten _prior_ to reading the image back. Or
it should be, obviously it was not in your casee.

> lines to ensure that it won't accidentally have the same contents as the
> previous image's header.
> 
> The hash doesn't have to be MD5; even a CRC should suffice I think...

But the failure you have seen now - failure to invalidate the resume
header - could also happen as long as we do not fix the reason for your
failure. If we fix it, we don't need additional security nets ;-)

But i have no idea what went wrong for you, i'll have a look at the code
but i doubt that i'll find much of interest.

One thing which would be interesting:
You don't eventually have multiple swap partitions?
-- 
Stefan Seyfried                  \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \                    -- Leonard Cohen