linux-ext4 - Re: [PATCH V2] mke2fs.8.in: clarify the sign of a block-size constraint.

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]

Date:	Fri, 30 Jul 2010 20:40:58 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Chris Frost <chris@...stnet.net>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH V2] mke2fs.8.in: clarify the sign of a block-size
 constraint.

On Thu, Jul 29, 2010 at 11:59:42AM -0500, Eric Sandeen wrote:
> This bit of the mke2fs manpage is slightly confusing:
> 
> -b block-size
>     Specify the size of blocks in bytes. <snip>
>     If block-size is negative, then mke2fs will use heuristics 
>     to determine the appropriate block size, with the constraint 
>     that the block size will be at least block-size bytes.
> 
> because it sounds like the block size will be at least a negative
> number.  Clarify just what the negative sign means.
> 
> Reported-by: Chris Frost <chris@...stnet.net>
> Signed-off-by: Eric Sandeen <sandeen@...hat.com>

Applied, thanks.

					- 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