linux-ext4 - Re: [PATCH] EXT_MAX

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <1215523338.3249.18.camel@alpha.linsyssoft.com>
Date:	Tue, 08 Jul 2008 18:52:18 +0530
From:	Girish Shilamkar <Girish.Shilamkar@....COM>
To:	Ext4 Mailing List <linux-ext4@...r.kernel.org>
Cc:	adilger@....COM, Theodore Tso <tytso@....edu>
Subject: Re: [PATCH] EXT_MAX_BLOCK for >= 16TB fs

Oops ...

On Tue, 2008-07-08 at 18:21 +0530, Girish Shilamkar wrote:
> Hi,	
> 	Here is the patch for same.
> 
> Thanks,
> Girish
> 
> On Mon, 2008-07-07 at 22:25 +0530, Girish Shilamkar wrote:
> > Hi,
> > 	The magic constant EXT_MAX_BLOCK = 0xffffffff in extents code is used
> > in some places to return "invalid block number", and to set the extent
> > length = "whole file" in other places.
> > 	So with >= 16 TB fs we would prefer to use it differently. We can have
> > EXT_UNSET_BLOCK = 1 to indicate "invalid block number" as it will never
> > be valid block for allocation. And for "whole file" usecase we can
> > continue using current EXT_MAX_BLOCK
> > 
> > Regards,
> > Girish
> > 
> > 
> > 
> > --
> > 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
> 
> --
> 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

View attachment "Fix-EXT_MAX_BLOCK.patch" of type "text/x-patch" (84626 bytes)