linux-ext4 - Re: [RFC][PATCH 11/11][take 2] 48-bit block number for ACL in e2fsprogs

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

Date:	Thu, 21 Jun 2007 16:44:28 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Valerie Clement <valerie.clement@...l.net>
Cc:	Theodore Tso <tytso@....edu>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [RFC][PATCH 11/11][take 2] 48-bit block number for ACL in e2fsprogs

On Jun 21, 2007  17:49 +0200, Valerie Clement wrote:
> This patch is intended to contain the changes to support 48-bit block
> numbers for ACL. For now, it only contains modifications in the inode
> structure. It has to be completed.
> 
> Andreas proposed to rename i_file_acl to i_file_ea
> and i_file_acl_high to i_file_ea_hi.

Yes, it is misleading that these are called "ACL", since the ACL is only
optionally stored internal to the EA block.  We should provide compatibility
macros to avoid breaking old code, which will also allow incremental
migration.

> @@ -449,6 +450,7 @@ struct ext2_inode_large {
>  #define i_reserved1	osd1.masix1.m_i_reserved1
>  #define i_frag		osd2.masix2.m_i_frag
>  #define i_fsize		osd2.masix2.m_i_fsize
> +#define i_file_acl_high	osd2.masix2.m_i_file_acl_high
>  #define i_reserved2	osd2.masix2.m_i_reserved2

On an unrelated note - does MASIX even exist anymore?  I think it was only
a very experimental OS that Rémy Card worked on, and the home page doesn't
even exist anymore.

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