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: <170fa0d20806042028r738795d2h6b6452ecb3e0f4b7@mail.gmail.com> Date: Wed, 4 Jun 2008 23:28:09 -0400 From: "Mike Snitzer" <snitzer@...il.com> To: "Theodore Tso" <tytso@....edu>, "Andrew Morton" <akpm@...ux-foundation.org>, "Jan Kara" <jack@...e.cz>, "Hidehiro Kawai" <hidehiro.kawai.ez@...achi.com>, sct@...hat.com, adilger@....com, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, jbacik@...hat.com, cmm@...ibm.com, yumiko.sugita.yf@...achi.com, satoshi.oshima.fk@...achi.com Subject: Re: [PATCH 1/5] jbd: strictly check for write errors on data buffers On Wed, Jun 4, 2008 at 5:22 PM, Theodore Tso <tytso@....edu> wrote: > That being said, ext3 can be tuned (and it is the default today, > although I should probably change the default to be remount-ro), so > that its behaviour on write errors is, "don't worry, be happy", and > just leave the filesystem mounted read/write. That's actually quite > dangerous for a critical production server, however..... I'm not completely sure which "it" you mean in "it is the default today" (seems like you mean errors=continue) but isn't remount-ro already the ext3 default? see commit: 1eca93f9cafdec4a332ace9b0fc0d3886d430c28 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists