| 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
| ||
|
Message-ID: <20080519085842.GA2013@elf.ucw.cz> Date: Mon, 19 May 2008 10:58:42 +0200 From: Pavel Machek <pavel@...e.cz> To: Eric Sandeen <sandeen@...hat.com> Cc: ext4 development <linux-ext4@...r.kernel.org>, linux-kernel Mailing List <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Jamie Lokier <jamie@...reable.org> Subject: Re: [PATCH 1/4] ext3: enable barriers by default On Fri 2008-05-16 14:05:55, Eric Sandeen wrote: > I can't think of any valid reason for ext3 to not use barriers when > they are available; I believe this is necessary for filesystem > integrity in the face of a volatile write cache on storage. > > An administrator who trusts that the cache is sufficiently battery- > backed (and power supplies are sufficiently redundant, etc...) > can always turn it back off again. > > SuSE has carried such a patch for quite some time now. > > Also document the mount option while we're at it. > > Signed-off-by: Eric Sandeen <sandeen@...hat.com> > Acked-by: Jan Kara <jack@...e.cz> Yes please. Safe defaults are the way to go. 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