linux-kernel - Re: ext3 seems to ignore ECC 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] [day] [month] [year] [list]

Date:	Mon, 4 Aug 2008 12:51:56 -0400
From:	Theodore Tso <tytso@....edu>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	Andreas Schwab <schwab@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: ext3 seems to ignore ECC errors

On Mon, Aug 04, 2008 at 04:47:27PM +0100, Samuel Thibault wrote:
> Andreas Schwab, le Mon 04 Aug 2008 17:39:06 +0200, a écrit :
> > Samuel Thibault <samuel.thibault@...-lyon.org> writes:
> > > However, to my surprise Linux (2.6.26) continued to mount the ext3
> > > filesystem read/write, spitting out a lot of IDE errors.  Shouldn't
> > > filesystems remount read-only and let the admin try to save data in such
> > > case?
> > 
> > That's a tunable parameter of the filesystem, see tune2fs(8).
> 
> Oh, I had assumed it was on by default, hum.  But now it reads
> 
> Errors behavior:          Remount read-only
> 
> and I am still getting the same behavior.  Indeed after some VFS
> modifications time it gets remounted read-only, but shouldn't that
> happen as soon as possible?

Errors writing to data blocks should get reflected up the application
(i.e., as EIO errors), but it won't force the filesystem read/only or
force a kernel panic (in the "tune2fs -e panic" case).  The rationale
being if it's a single isloated error writing to a single file, why
ruin everybody's day by taking more drastic action?

But if we can't write to core filesystem data structures, that's a
much more serious situation....

						- Ted
--
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/