linux-ext4 - Re: What is fragment in ext3/4 ?

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] [day] [month] [year] [list]

Message-ID: <20070803222859.GX6142@schatzie.adilger.int>
Date:	Fri, 3 Aug 2007 16:28:59 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Coly Li <colyli@...il.com>
Cc:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: What is fragment in ext3/4 ?

On Aug 04, 2007  00:20 +0800, Coly Li wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Eric Sandeen wrote:
> > There's a fair amount of code around this never-implemented concept;
> > should it be removed?  :)
> 
> I agree with this idea. It seems we will never implement it in future,
> once "fragment" packed into inode.

Yes, this should all be removed.  In fact, the "fragment" fields are
being reassigned in the upstream e2fsprogs, so there is no chance to
implement it in the future either.  If we ever want to have fragments
like this, the plan was to add them as EAs in the inode (no point to
make an external EA block to hold a block of data).

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
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