linux-ext4 - Re: [PATCH RFC 00/30] Ext4 snapshots

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]

Date:	Mon, 06 Jun 2011 21:58:45 +0200
From:	Lukáš Czerner <czerner.lukas@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
CC:	Andreas Dilger <aedilger@...il.com>,
	"Amir G." <amir73il@...rs.sourceforge.net>,
	Lukas Czerner <lczerner@...hat.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"tytso@....edu" <tytso@....edu>
Subject: Re: [PATCH RFC 00/30] Ext4 snapshots - core patches

Dne 6.6.2011 18:42, Eric Sandeen napsal(a):
>>> Take for example dioread_nolock caveats:
>>>
>>>           "However this does not work with nobh
>>>            option and the mount will fail.
>> Does anyone actually use nobh? I recall it was a performance tweak
>> fir ext3, but i think it was eclipsed by other improvements in ext4.
>> If nobody is using it anymore, we might consider removing it
>> entirely, since it was only a mount-time option and did not affect
>> the on-disk format.
> As Lukas said, removing old cruft would help a fair bit, and this would
> seem reasonable to remove.
Nobh has been nooped already quite a long time ago with
206f7ab4f49a2021fcb8687f25395be77711ddee so we should remove it from 
documentation as well.

And what about other options ? Any idea what else we can remove ? Most 
of the options does not get any testing at all!

Thanks!
-Lukas
--
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