| 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: Sat, 29 Aug 2009 12:05:58 +0200 From: Pavel Machek <pavel@....cz> To: david@...g.hm Cc: Rob Landley <rob@...dley.net>, Ric Wheeler <rwheeler@...hat.com>, Theodore Tso <tytso@....edu>, Florian Weimer <fweimer@....de>, Goswin von Brederlow <goswin-v-b@....de>, kernel list <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com, rdunlap@...otime.net, linux-doc@...r.kernel.org, linux-ext4@...r.kernel.org, corbet@....net Subject: Re: [patch] ext2/3: document conditions when reliable operation is possible On Fri 2009-08-28 07:49:38, david@...g.hm wrote: > On Thu, 27 Aug 2009, Rob Landley wrote: > >> Pavel's response was to attempt to document this. Not that journaling is >> _bad_, but that it doesn't protect against this class of problem. > > I don't think anyone is disagreeing with the statement that journaling > doesn't protect against this class of problems, but Pavel's statements > didn't say that. he stated that ext3 is more dangerous than ext2. Well, if you use 'common' fsck policy, ext3 _is_ more dangerous. But I'm not pushing that to documentation, I'm trying to push info everyone agrees with. (check the patches). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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