linux-ext4 - Re: [PATCH 2/2] ext2: Avoid rec_len overflow with 64KB block 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: <20071018021155.0b648616.akpm@linux-foundation.org>
Date:	Thu, 18 Oct 2007 02:11:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Christoph Lameter <clameter@....com>
Cc:	Jan Kara <jack@...e.cz>, cmm@...ibm.com,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	sho@...s.nec.co.jp
Subject: Re: [PATCH 2/2] ext2: Avoid rec_len overflow with 64KB block size

On Thu, 18 Oct 2007 02:03:39 -0700 (PDT) Christoph Lameter <clameter@....com> wrote:

> On Wed, 17 Oct 2007, Andrew Morton wrote:
> 
> > b) what happens when an old ext2 driver tries to read and/or write this
> >    directory entry?  Do we need a compat flag for it?
> 
> Old ext2 only supports up to 4k
> 
> include/linux/ext2_fs.h:
> 
> #define EXT2_MIN_BLOCK_SIZE             1024
> #define EXT2_MAX_BLOCK_SIZE             4096
> #define EXT2_MIN_BLOCK_LOG_SIZE           10
> 
> Should fail to mount the volume since the block size is too large.

should, but does it?

box:/usr/src/25> grep MAX_BLOCK_SIZE fs/ext2/*.[ch] include/linux/ext2*
include/linux/ext2_fs.h:#define EXT2_MAX_BLOCK_SIZE             4096
box:/usr/src/25> 

-
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