linux-ext4 - Re: [PATCH] libext2fs: reserve exclude bitmap fields in group descriptor

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: <CAOQ4uxi0Xq89Va_ttTGJGZO342Mpa7HG03DhjhEsfHsubeso7A@mail.gmail.com>
Date:	Thu, 15 Sep 2011 16:47:17 +0300
From:	Amir Goldstein <amir73il@...il.com>
To:	"Ted Ts'o" <tytso@....edu>
Cc:	Andreas Dilger <adilger.kernel@...ger.ca>,
	"Darrick J. Wong" <djwong@...ibm.com>,
	Sunil Mushran <sunil.mushran@...cle.com>,
	Andi Kleen <andi@...stfloor.org>,
	Mingming Cao <cmm@...ibm.com>,
	Joel Becker <jlbec@...lplan.org>, linux-ext4@...r.kernel.org,
	Coly Li <colyli@...il.com>,
	Yongqiang Yang <xiaoqiangnk@...il.com>
Subject: Re: [PATCH] libext2fs: reserve exclude bitmap fields in group descriptor

On Thu, Sep 15, 2011 at 4:16 PM, Ted Ts'o <tytso@....edu> wrote:
> On Thu, Sep 15, 2011 at 09:50:20AM +0300, Amir Goldstein wrote:
>> -#define EXT2_FEATURE_COMPAT_EXCLUDE_INODE      0x0080
>> +/* #define EXT2_FEATURE_COMPAT_EXCLUDE_INODE   0x0080 not used */
>> +#define EXT2_FEATURE_COMPAT_EXCLUDE_BITMAP     0x0100
>
> Why this change?  Is it because you're already using 0x0100 in
> shipping systems?
>

I am using 0x80 in shipping systems and it signifies something a bit
different then
the proposed 0x100.

EXCLUDE_INODE means that special inode 9 is used to reference exclude
bitmap blocks.
EXCLUDE_BITMAP means that exclude bitmap blocks are referenced from
group descriptors.
With this distinction it will be easier for me to make the migration.

Thanks,
Amir.
--
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