linux-kernel - Re: ext3 defaults to errors=continue, why?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.00.0812270341310.24239@bogon.housecafe.de>
Date:	Sat, 27 Dec 2008 03:58:18 +0100 (CET)
From:	Christian Kujau <lists@...dbynature.de>
To:	Pavel Machek <pavel@...e.cz>
cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: ext3 defaults to errors=continue, why?

On Fri, 26 Dec 2008, Pavel Machek wrote:
> I don't know where errors=continue came from (and I think its
> dangerous);

In lib/ext2fs/ext2_fs.h (from e2fsprogs) a default is set:

#define EXT2_ERRORS_CONTINUE		1	/* Continue execution */
#define EXT2_ERRORS_RO			2	/* Remount fs read-only */
#define EXT2_ERRORS_PANIC		3	/* Panic */
#define EXT2_ERRORS_DEFAULT		EXT2_ERRORS_CONTINUE

...which is then referenced in lib/ext2fs/initialize.c - but I agree, I 
find this dangerous myself and the first thing I do after mkfs is always 
to tune2fs to remount-ro.

Christian.
-- 
BOFH excuse #39:

terrorist activities
--
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/