linux-ext4 - Re: [PATCH 2/3] mke2fs: reduce the range of cluster-size

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: <20130114211014.GA22642@thunk.org>
Date:	Mon, 14 Jan 2013 16:10:14 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Andreas Dilger <adilger@...ger.ca>
Cc:	Zheng Liu <gnehzuil.liu@...il.com>, linux-ext4@...r.kernel.org,
	Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PATCH 2/3] mke2fs: reduce the range of cluster-size

On Mon, Jan 14, 2013 at 02:07:43PM -0700, Andreas Dilger wrote:
> > I think the best way of fixing this is to document that the -g option
> > specifies the number of clusters per block if the bigalloc feature is
> > enabled.
> 
> Presumably you mean "the -g option specifies the number of clusters
> _per_group_ if the bigalloc feature is enabled"?

Yes, I meant to say that I want to change the definition of the -g
option such that if the bigalloc feature is enabled, it specifies the
number of clusters per block group.

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