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]

Message-ID: <CAFLxGvz4MUQrLUs=CWVbWspKQoBC7qiLTUyWQMKzgeX8r3L8VA@mail.gmail.com>
Date:	Fri, 17 Feb 2012 00:37:17 +0100
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Dave Jones <davej@...hat.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org, esandeen@...hat.com
Subject: Re: Corrupted files after suspend to disk

On Fri, Feb 17, 2012 at 12:27 AM, Eric Sandeen <sandeen@...hat.com> wrote:
> On 2/16/12 8:30 AM, Dave Jones wrote:
>> On Thu, Feb 16, 2012 at 11:52:27AM +0100, richard -rw- weinberger wrote:
>>
>>  > >> >> Of course, please test the above separately. :-)
>>  > >> >
>>  > >> > Ok, I'll test this when I'm at home.
>>  > >> >
>>  > >> > BTW: dropping the caches helps, when some files seem corrupted.
>>  > >> > Today /usr/bin/okular was broken.
>>  > >> > After setting vm.drop_caches=1 it worked again.
>>  > >>
>>  > >> On Linux 2.6.38 I'm unable to reproduce the issue.
>>  > >> Only 2.6.37 seems to be affected.
>>  > >> So, I'm moving over to 2.6.38. :)
>>  > >
>>  > Bad news:
>>  > I saw the issue on 3.x too but thought it's because my IdeaPad s10 is crap.
>>  > Now with my shiny new Lenovo x121e I have the same issue! :-(
>>  >
>>  > OpenSUSE 12.1, kernel 3.2.7.
>>  > After a few suspend2disk iterations random files are corrupted.
>>  > But only cached files. A reboot solves the problem.
>
> Just to be clear - you see _data_ corruption in files, but only
> until a reboot, and after that they are ok?  Ok, reading above
> about using drop_caches that sounds like the case.

Yes.
A reboot always solved the data corruption.
drop_caches solved it in 99% of all cases.

On-disk data was never corrupted.

-- 
Thanks,
//richard
--
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/