linux-kernel - Re: [RFC][PATCH 13/14] ext3 whiteout support

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]

Date:	Mon, 14 May 2007 22:35:47 +0200
From:	"Jan Blunck" <jblunck@...e.de>
To:	"Bharata B Rao" <bharata@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	"Jan Blunck" <j.blunck@...harburg.de>,
	"Theodore Ts'o" <tytso@....edu>
Subject: Re: [RFC][PATCH 13/14] ext3 whiteout support

On 5/14/07, Andreas Dilger <adilger@...sterfs.com> wrote:
> On May 14, 2007  15:14 +0530, Bharata B Rao wrote:
> >  #define EXT3_FEATURE_INCOMPAT_JOURNAL_DEV    0x0008 /* Journal device */
> >  #define EXT3_FEATURE_INCOMPAT_META_BG                0x0010
> > +#define EXT3_FEATURE_INCOMPAT_WHITEOUT               0x0020
>
> Is this flag reserved with Ted?  It isn't listed in the e2fsprogs repo.
>

I don't know. I tried to contact him a few weeks ago but failed.
Guess, maybe he isn't reading the @thunk.org email anymore which was
reference in the e2fsprogs source I used.

Ted,
from ext2_fs.h I learn that the value 0x0020 is left unused.

#define EXT2_FEATURE_INCOMPAT_META_BG           0x0010
#define EXT3_FEATURE_INCOMPAT_EXTENTS           0x0040
#define EXT4_FEATURE_INCOMPAT_64BIT             0x0080

Is this intentionally?

Cheers,
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/