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: <20090107053250.GA9617@skywalker>
Date:	Wed, 7 Jan 2009 11:02:50 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: Remove "extents" mount option

On Tue, Jan 06, 2009 at 01:49:37PM -0500, Theodore Ts'o wrote:
> This mount option is largely superfluous, and in fact the way it was
> implemented was buggy; if a filesystem which did not have the extents
> feature flag was mounted -o extents, the filesystem would attempt to
> create and use extents-based file even though the extents feature flag
> was not eabled.  The simplest thing to do is to nuke the mount option
> entirely.  It's not all that useful to force the non-creation of new
> extent-based files if the filesystem can support it.
> 

Ext4 -> Ext3 migration story is to mount the filesystem with -o
noextents and copy the file around. If we remove the -o noextents
options how do we force the creation of non extent format files ?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ