linux-ext4 - Re: [PATCH] ext3: make "norecovery" an alias for "noload"

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]

Message-ID: <4B06B898.1010606@redhat.com>
Date:	Fri, 20 Nov 2009 09:41:12 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	tytso@....edu
CC:	Jan Kara <jack@...e.cz>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext3: make "norecovery" an alias for "noload"

tytso@....edu wrote:
> On Thu, Nov 19, 2009 at 04:12:33PM +0100, Jan Kara wrote:
>> On Mon 16-11-09 16:50:49, Eric Sandeen wrote:
>>> Users on the list recently complained about differences across
>>> filesystems w.r.t. how to mount without a journal replay.
>>>
>>> In the discussion it was noted that xfs's "norecovery" option is
>>> perhaps more descriptively accurate than "noload," so let's make
>>> that an alias for ext3.
>>>
>>> Also show this status in /proc/mounts
>>>
>>> Signed-off-by: Eric Sandeen <sandeen@...hat.com>
>>   OK, provided ext4 will have the same change, I'm fine with the patch.
>> So how is it with ext4?
> 
> Queued for the next merge window.  I did slightly change the
> documentation in Documentation/filesystems/ext4.txt to make
> "norecovery" be the canonnical option name, since that's what Eric had
> show up in /proc/mounts.  That seems fair, we might as well try to add
> consistency between different Linux filesystems.
> 
> 							- Ted

FWIW, the nilfs folks just added an option to do the same thing, and
I steered them towards "norecovery" - we may just get some consistency,
yet!

-Eric
--
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