From: Andreas Dilger <adilger@dilger.ca>
To: Aditya Kali <adityakali@google.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] e2fsprogs: reserving code points for new ext4 quota feature
Date: Mon, 14 Feb 2011 22:21:49 -0700 [thread overview]
Message-ID: <BD2A37BD-B970-4520-A8AB-589249C96755@dilger.ca> (raw)
In-Reply-To: <AANLkTik3Ff7jokEL47uaLphwAP9hcd_16-eb3P8Cvagf@mail.gmail.com>
On 2011-02-14, at 18:07, Aditya Kali <adityakali@google.com> wrote:
> This patch adds support for detecting the new 'quota' feature in ext4.
> The patch reserves code points for usr and group quota inodes and also
> for the feature flag EXT4_FEATURE_RO_COMPAT_QUOTA.
>
> diff --git a/lib/ext2fs/ext2_fs.h b/lib/ext2fs/ext2_fs.h
> index fee3919..74f5a2f 100644
> --- a/lib/ext2fs/ext2_fs.h
> +++ b/lib/ext2fs/ext2_fs.h
> @@ -52,6 +52,9 @@
> #define EXT2_JOURNAL_INO 8 /* Journal inode */
> #define EXT2_EXCLUDE_INO 9 /* The "exclude" inode, for snapshots */
>
> +#define EXT4_USR_QUOTA_INO 3 /* User quota inode */
> +#define EXT4_GRP_QUOTA_INO 4 /* Group quota inode */
This is missing the fact that ino 3 and 4 are already reserved for ACLs:
#define EXT2_ACL_IDX_INO 3 /* ACL inode */
#define EXT2_ACL_DATA_INO 4 /* ACL inode */
That said, I don't know if those inodes are actually ever used, because the ACLs are stored in xattrs on each inode.
In any case, the quota definitions should replace the ACL ones instead of being hidden after the main list (which is otherwise kept in numeric order).
Cheers, Andreas
next prev parent reply other threads:[~2011-02-15 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 1:07 [PATCH] e2fsprogs: reserving code points for new ext4 quota feature Aditya Kali
2011-02-15 4:39 ` Amir Goldstein
2011-02-15 5:21 ` Andreas Dilger [this message]
2011-02-15 17:07 ` Ted Ts'o
2011-02-15 19:54 ` Aditya Kali
2011-02-15 20:45 ` Andreas Dilger
2011-02-15 22:27 ` Aditya Kali
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=BD2A37BD-B970-4520-A8AB-589249C96755@dilger.ca \
--to=adilger@dilger.ca \
--cc=adityakali@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox