From: "Jose R. Santos" <jrs@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 8/9][e2fsprogs] Add 64-bit closefs interface.
Date: Mon, 12 May 2008 12:24:43 -0500 [thread overview]
Message-ID: <20080512122443.7ef72b19@gara> (raw)
In-Reply-To: <20080512150550.GF7029@mit.edu>
On Mon, 12 May 2008 11:05:50 -0400
Theodore Tso <tytso@mit.edu> wrote:
> On Fri, May 09, 2008 at 11:40:19AM -0500, Jose R. Santos wrote:
> > From: Jose R. Santos <jrs@us.ibm.com>
> >
> > Add 64-bit closefs interface.
> >
> > Add new ext2fs_super_and_bgd_loc2() that returns blk64_t pointers.
> > The function now returns the number of blocks used by super block and
> > group descriptors since with flex_bg, it can no longer be assumed that
> > bitmaps and inode tables still resided within the block group.
>
> This change makes me nervous, because (a) I need to assure myself that
> ext2fs_super_and_bgd_loc() is going to always do the right thing, and
> (b) the changes to the callers of ext2fs_super_and_bgd_loc2() aren't
> also described.
I thought that we concluded that ext2fs_super_and_bgd_loc() would not
do the right thing which is the reason that ext2fs_super_and_bgd_loc2()
returns just the number of groups used by super block and group
descriptors. Right now, ext2fs_super_and_bgd_loc() works the same as
it has before, and the new ext2fs_super_and_bgd_loc2() would do the
right thing here by not assuming inode tables and bitmaps are located
in the block group.
> So this requires more thought. One change I would make is to return
> the number of blocks via a pointer rather than through a straight
> return value. And also, if I recall correctly, nothing is actually
> using the ret_meta_bg pointer, so we might be able to drop that in the
> _2 version. of the interface.
I will make these two changes.
> We should probably include in this patch series the callers of
> ext2fs_super_and_bgd_loc() and assure ourselves that the new interface
> actually works correctly and is clean for the users before we finalize
> the interface change.
Fair enough. I'll add a patch for this.
> - Ted
-JRS
next prev parent reply other threads:[~2008-05-12 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:39 [RFC PATCH 0/9][e2fsprogs] Initial blk64_t capable API calls Jose R. Santos
2008-05-09 16:39 ` [RFC PATCH 1/9][e2fsprogs] Add ext2_off64_t type Jose R. Santos
2008-05-09 16:39 ` [RFC PATCH 2/9][e2fsprogs] Use blk64_t for blocks in struct ext2_file Jose R. Santos
2008-05-09 16:39 ` [RFC PATCH 3/9][e2fsprogs] Add 64-bit dirblock interface Jose R. Santos
2008-05-09 16:39 ` [RFC PATCH 4/9][e2fsprogs] Add 64-bit alloc_stats interface Jose R. Santos
2008-05-12 14:43 ` Theodore Tso
2008-05-12 17:25 ` Jose R. Santos
2008-05-09 16:39 ` [RFC PATCH 5/9][e2fsprogs] Add 64-bit alloc interface Jose R. Santos
2008-05-09 16:40 ` [RFC PATCH 6/9][e2fsprogs] Add 64-bit ext_attr interface Jose R. Santos
2008-05-12 14:47 ` Theodore Tso
2008-05-09 16:40 ` [RFC PATCH 7/9][e2fsprogs] Add new blk64_t handling inline functions Jose R. Santos
2008-05-12 14:49 ` Theodore Tso
2008-05-12 17:25 ` Jose R. Santos
2008-05-12 19:22 ` Theodore Tso
2008-05-09 16:40 ` [RFC PATCH 8/9][e2fsprogs] Add 64-bit closefs interface Jose R. Santos
2008-05-12 15:05 ` Theodore Tso
2008-05-12 17:24 ` Jose R. Santos [this message]
2008-05-12 19:29 ` Theodore Tso
2008-05-09 16:40 ` [RFC PATCH 9/9][e2fsprogs] Add 64-bit openfs interface 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=20080512122443.7ef72b19@gara \
--to=jrs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).