All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>, Mingming Cao <cmm@us.ibm.com>
Subject: ext4_inode difference between e2fsprogs and ext4
Date: Thu, 11 Oct 2007 14:30:48 +0530	[thread overview]
Message-ID: <470DE640.3040101@linux.vnet.ibm.com> (raw)

in e2fsprogs we have

union { 
                struct {
                        __u16   l_i_blocks_hi;
                        __u16   i_pad1;
                        __u16   l_i_uid_high;   /* these 2 fields    */
                        __u16   l_i_gid_high;   /* were reserved2[0] */
                        __u32   l_i_reserved2;
                } linux2;



In ext4 we have

  union { 
                struct {
                        __le16  l_i_reserved1;  /* Obsoleted fragment number/size which are removed in ext4 */
                        __le16  l_i_file_acl_high;
                        __le16  l_i_uid_high;   /* these 2 fields */
                        __le16  l_i_gid_high;   /* were reserved2[0] */
                        __u32   l_i_reserved2;
                } linux2;


Last week we were discussing about taking that l_i_reserved1 and using that for making file_acl 64 bit and using the
lower l_i_reserved2 for 64 bit dir_acl. 

Now where will i put l_i_blocks_hi ?

-aneesh

             reply	other threads:[~2007-10-11  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  9:00 Aneesh Kumar K.V [this message]
2007-10-11  9:19 ` ext4_inode difference between e2fsprogs and ext4 Andreas Dilger

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=470DE640.3040101@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.