| 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 22:29:30 -0300 From: Henrique de Moraes Holschuh <hmh@....eng.br> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: linux-pm@...ts.linux-foundation.org, Maxim Levitsky <maximlevitsky@...il.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [linux-pm] Massive ext4 filesystem corruption after a failed s2disk/ram cycle On Wed, 07 Oct 2009, Rafael J. Wysocki wrote: > On Wednesday 07 October 2009, Henrique de Moraes Holschuh wrote: > > On Tue, 06 Oct 2009, Rafael J. Wysocki wrote: > > > > You do sync file-systems before entering the hibernation, don't you? > > > > > > Yes, a sync is there, but it is not effective on some filesystems. > > > > Which ones? > > XFS for one example. Interesting. So XFS is not only a Bad Idea for /, but also for anything that might enter S3/S4. Not nice. I sure hope it doesn't do a half-assed job of flushing and checkpointing itself during machine shutdown/restart like it apparently does when told to "sync" before S3/S4... Would you be so kind to disclose to us, the uninitated, which other filesystems are unsafe when faced with a sleep/suspend request? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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