From: Theodore Tso <tytso@MIT.EDU>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Andreas Dilger <adilger@sun.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: New bitmap and inode table allocation for FLEX_BG
Date: Sun, 10 Feb 2008 23:33:51 -0500 [thread overview]
Message-ID: <20080211043351.GD26205@mit.edu> (raw)
In-Reply-To: <20080208113740.11760ee2@gara>
On Fri, Feb 08, 2008 at 11:37:40AM -0600, Jose R. Santos wrote:
> > > #define EXT2_BG_INODE_UNINIT 0x0001 /* Inode table/bitmap not initialized */
> > > #define EXT2_BG_BLOCK_UNINIT 0x0002 /* Block bitmap not initialized */
> > > +#define EXT2_BG_FLEX_METADATA 0x0004 /* FLEX_BG block group contains meta-data */
> >
> > Hrm, I thought I had reserved that value in the uninit_groups patch?
> > +#define EXT3_BG_INODE_ZEROED 0x0004 /* On-disk itable initialized to zero */
>
> I may have been, I just based the patch on the next branch as Ted had
> ask for new e2fsprog patches. The uninit group patch was not part of
> the next branch when I pulled.
Yes, but whenever you start reserving code points that impact the
on-disk format, you need to be careful and coordinate. Exactly is the
purpose of this flag, and why is it here?
And I don't see any patch in the kernel patch queue that uses this
flag. Is this intended for internal use inside e2fsprogs? If so,
this might not be the best place for it.....
- Ted
next prev parent reply other threads:[~2008-02-11 4:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 17:09 [PATCH] e2fsprogs: New bitmap and inode table allocation for FLEX_BG Jose R. Santos
2008-02-08 5:11 ` Andreas Dilger
2008-02-08 17:37 ` Jose R. Santos
2008-02-11 4:33 ` Theodore Tso [this message]
2008-02-11 15:05 ` Jose R. Santos
-- strict thread matches above, loose matches on Subject: below --
2008-04-01 3:13 [PATCH][e2fsprogs] " Jose R. Santos
2008-04-03 13:12 ` Theodore Tso
2008-04-03 14:28 ` Jose R. Santos
2008-04-04 3:24 ` Theodore Tso
2008-04-04 5:37 ` Jose R. Santos
2008-04-04 12:43 ` Theodore Tso
2008-04-04 15:20 ` Jose R. Santos
2008-01-11 17:28 [PATCH] e2fsprogs: " Jose R. Santos
2008-01-11 21:01 ` Andreas Dilger
2008-01-11 22:11 ` Jose R. Santos
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=20080211043351.GD26205@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=jrs@us.ibm.com \
--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 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.