From: Andreas Dilger <adilger@clusterfs.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH 11/11][take 2] 48-bit block number for ACL in e2fsprogs
Date: Thu, 21 Jun 2007 16:44:28 -0600 [thread overview]
Message-ID: <20070621224428.GE5181@schatzie.adilger.int> (raw)
In-Reply-To: <467A9E02.5030701@bull.net>
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.
prev parent reply other threads:[~2007-06-21 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 15:49 [RFC][PATCH 11/11][take 2] 48-bit block number for ACL in e2fsprogs Valerie Clement
2007-06-21 22:44 ` Andreas Dilger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070621224428.GE5181@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=valerie.clement@bull.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox