| 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
| ||
|
Date: Tue, 6 Oct 2009 17:42:14 -0400 From: Theodore Tso <tytso@....edu> To: Maxim Levitsky <maximlevitsky@...il.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, linux-pm <linux-pm@...ts.linux-foundation.org> Subject: Re: Massive ext4 filesystem corruption after a failed s2disk/ram cycle On Tue, Oct 06, 2009 at 11:06:55PM +0200, Maxim Levitsky wrote: > > Just prior to 2.6.32 cycle I tried -next tree and noticed that after a > failed s2ram (here it works only once, and I test once in a whileto see > if fixed accidentally) I got a minor filesystem corruption. I am sorry I > didn't report that back then. When you say filesystem corruption, it's important to indicate whether you meant that (a) you noticed that some files were had corrupted contents, (b) the kernel complained that the filesystem was corrupted, and remounted the filesystem read-only, or (c) e2fsck found and fixed errors. Also, when you found errors of either class (a) or (b), did you run e2fsck to find and fix any potential errors? In a few places it sounded like the kernel had complained about errors, but you had ignored them and hadn't run e2fsck to fix them. I hope that was just me misunderstanding what you wrote! Can you clarify? - Ted -- 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/
Powered by blists - more mailing lists