linux-kernel - Re: Corrupted files after suspend to disk

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:	Fri, 16 Mar 2012 16:19:33 +0100
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Dave Jones <davej@...hat.com>,
	Andreas Hartmann <andihartmann@...19freenet.de>,
	Jiri Kosina <jkosina@...e.cz>,
	richard -rw- weinberger <richard.weinberger@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
	keithp@...thp.com
Subject: Re: Corrupted files after suspend to disk

On Mon, Mar 12, 2012 at 10:49 PM, Dave Jones <davej@...hat.com> wrote:
> if you compare the hexdump of the good/bad files, you find that the corruption
> happens in 8x 4 byte writes of either 0x00000000 or 0x00aaaaaa.

Yeah, it looks like the described pattern.
The attached diff shows four 8x4 byte writes of 0x00000000.

-- 
Thanks,
//richard

View attachment "hexdump.diff" of type "text/x-patch" (3093 bytes)