linux-ext4 - Re: EXT3 way too happy with write errors

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081218172759.GE13580@duck.suse.cz>
Date:	Thu, 18 Dec 2008 18:27:59 +0100
From:	Jan Kara <jack@...e.cz>
To:	Simon Kirby <sim@...nation.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: EXT3 way too happy with write errors

On Thu 18-12-08 09:18:25, Simon Kirby wrote:
> > we spotted a write error in filesystem metadata. If we spotted an error
> > in data, we just complained but continued. This seems to be exactly the
> > thing you are hitting. Latest Linus's tree (i.e. 2.6.28-rc5 or so) should
> > have the patches that allow tuning the behavior in data=ordered mode - i.e.
> > you can tell the filesystem by data_err=abort and data_err=ignore option
> > whether it should abort the filesystem or ignore write error in fs data.
> 
> Cool, but one question.. Can you think of a case where anyone would ever
> want data_err=ignore?
> 
> Should this really be a knob?
  Originally, we changed the behavior unconditionally but then someone came
up with some reasonable argument why it should be tunable. I don't remember
it exactly, sorry :).

									Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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