Could the resource fork also keep ACLs? Looking up separate ACL
data and MAC data seems like it might be slow. The space saving
would help a great deal. So maybe rename i_*_acl and put privs
in there.
i_size_high could actually be a __u8, which gets us a terabyte.
I really wish all these ext2 projects would show some evidence
of communication, like a common inode format. It could go in
the kernel now even, with the code setting new stuff to 0.
In case it is of interest, here is how a directory could start.
(security from Digital Unix, performance hack from *BSD)
Maybe this is read-only compatible.
__u32 dot_ino;
__u16 dot_reclen;
__u8 dot_type; /* mode>>12 for Gnu /bin/ls and fsck */
__u8 dot_namlen;
char dot_name[4];
__u32 dot_sl; /* sensitivity label */
__u32 dot_il; /* info label */
__u32 dotdot_ino;
__u16 dotdot_reclen;
__u8 dotdot_type; /* mode>>12 for Gnu /bin/ls and fsck */
__u8 dotdot_namlen;
char dotdot_name[4];
__u32 dotdot_sl; /* sensitivity label */
__u32 dotdot_il; /* info label */