From: Andreas Dilger <adilger@clusterfs.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/2] Make ext3 use bit operations to manipulate i_flags
Date: Thu, 11 Oct 2007 14:08:32 -0600 [thread overview]
Message-ID: <20071011200832.GU8122@schatzie.adilger.int> (raw)
In-Reply-To: <20071011180111.GG7125@duck.suse.cz>
On Oct 11, 2007 20:01 +0200, Jan Kara wrote:
> #define EXT3_TOPDIR_FL 17 /* Top of directory hierarchies*/
> +#define EXT3_RTIME_FL 18 /* Update recursive mtime */
Could you please use "20" (0x100000) for this flag, as there were patches to
use 18 (0x40000) for EXT4_HUGE_FILE_FL, and 19 (0x80000) is definitely
reserved for EXT4_EXTENTS_FL.
I'd suggest emailing Ted to reserve a flag for this, and also adding the
other reserved flags to ext2 and ext3 so there is no risk of conflicts.
> @@ -572,6 +576,7 @@ static inline int ext3_valid_inum(struct
> #define EXT3_FEATURE_COMPAT_EXT_ATTR 0x0008
> #define EXT3_FEATURE_COMPAT_RESIZE_INODE 0x0010
> #define EXT3_FEATURE_COMPAT_DIR_INDEX 0x0020
> +#define EXT3_FEATURE_COMPAT_RTIME 0x0040
Similarly, there is already
#define EXT2_FEATURE_COMPAT_LAZY_BG 0x0040
in e2fsprogs so you need to use 0x0080 for your feature. Please update
all of the ext*_fs.h files to have the most recent flags from e2fsprogs
so that we can avoid such dangers in the future.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2007-10-11 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 17:56 [PATCH 1/2] Make ext3 use bit operations to manipulate i_flags Jan Kara
2007-10-11 18:01 ` Jan Kara
2007-10-11 20:08 ` 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=20071011200832.GU8122@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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