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: <201202162251.47063.rjw@sisk.pl>
Date:	Thu, 16 Feb 2012 22:51:46 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Dave Jones <davej@...hat.com>
Cc:	"richard -rw- weinberger" <richard.weinberger@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org, esandeen@...hat.com
Subject: Re: Corrupted files after suspend to disk

On Thursday, February 16, 2012, 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.
>  
> FWIW, we've been seeing a number of hard to diagnose failures
> with suspend to disk for the last few releases in Fedora.
> Eric Sandeen has been chasing https://bugzilla.redhat.com/show_bug.cgi?id=744275
> for a while, but there's no smoking gun that really explains what's
> getting into these states. Further complicating things, is that it
> doesn't seem to be 100% reproducable.

I wonder if that's reproducible with the filesystems freezing patch I posted
some time ago (it will need some rebasing to apply to the current mainline or
3.2.y).

I also thing that this problem discovered by Alan Stern may be involved:

http://marc.info/?l=linux-pm&m=132940331030253&w=4

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