From: Andreas Dilger <adilger@sun.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Tweedie <sct@redhat.com>,
adilger@clusterfs.com, Mingming Cao <cmm@us.ibm.com>,
Theodore Tso <tytso@MIT.EDU>
Subject: Re: [PATCH] ext4: fix ext4_init_block_bitmap() for metablock block group
Date: Sun, 15 Jun 2008 23:19:00 -0600 [thread overview]
Message-ID: <20080616051859.GK3726@webber.adilger.int> (raw)
In-Reply-To: <20080615142455.GA3502@localhost.localdomain>
On Jun 15, 2008 23:24 +0900, Akinobu Mita wrote:
> When meta_bg feature is enabled and s_first_meta_bg != 0,
> ext4_init_block_bitmap() miscalculates the number of block used by
> the group descriptor table (0 or 1 for metablock block group)
Can you please clarify why the calculation is incorrect? I admit that
I didn't test with META_BG enabled, so it could well be wrong, but looking
at the code I can't understand why it is incorrect.
> @@ -121,12 +121,7 @@ unsigned ext4_init_block_bitmap(struct s
if (!EXT4_HAS_INCOMPAT_FEATURE(sb, EXT4_FEATURE_INCOMPAT_META_BG) ||
block_group < le32_to_cpu(sbi->s_es->s_first_meta_bg) *
sbi->s_desc_per_block) {
if (bit_max) {
bit_max += ext4_bg_num_gdb(sb, block_group);
bit_max +=
> le16_to_cpu(sbi->s_es->s_reserved_gdt_blocks);
> }
> } else { /* For META_BG_BLOCK_GROUPS */
> - int group_rel = (block_group -
> - le32_to_cpu(sbi->s_es->s_first_meta_bg)) %
> - EXT4_DESC_PER_BLOCK(sb);
> - if (group_rel == 0 || group_rel == 1 ||
> - (group_rel == EXT4_DESC_PER_BLOCK(sb) - 1))
> - bit_max += 1;
> + bit_max += ext4_bg_num_gdb(sb, block_group);
> }
As you can see, the "if" checks if the block group is before s_first_meta_bg
to treat it as a "normal" group, and only uses the "else" once beyond the
start of the s_first_meta_bg limit.
It definitely is less complex to use ext4_bg_num_gdb(), and this could
further be simplified by using ext4_bg_gdb_meta() in the "else" clause.
In fact, the whole if/else could be replaced with ext4_bg_num_gdb() if
it weren't for s_reserved_gdt_blocks.
Maybe it makes sense (cleaner code, less chance for bugs) to change the
ext4_bg_num_gdb() function to take a parameter on whether it should
include the s_reserved_gdt_blocks or not:
static unsigned long ext4_bg_num_gdb_nometa(struct super_block *sb, int group,
int reserved)
{
if (EXT4_HAS_RO_COMPAT_FEATURE(sb,
EXT4_FEATURE_RO_COMPAT_SPARSE_SUPER) &&
!ext4_group_sparse(group))
return 0;
return EXT4_SB(sb)->s_gdb_count +
reserved ? EXT4_SB(sb)->s_reserved_gdt_blocks : 0;
}
unsigned long ext4_bg_num_gdb(struct super_block *sb, int group, int reserved)
{
unsigned long first_meta_bg =
le32_to_cpu(EXT4_SB(sb)->s_es->s_first_meta_bg);
unsigned long metagroup = group / EXT4_DESC_PER_BLOCK(sb);
if (!EXT4_HAS_INCOMPAT_FEATURE(sb,EXT4_FEATURE_INCOMPAT_META_BG) ||
metagroup < first_meta_bg)
return ext4_bg_num_gdb_nometa(sb, group, reserved);
return ext4_bg_num_gdb_meta(sb, group);
}
The fewer places in the code that need to understand META_BG, the less
chance of having a bug. Now the code in ext4_init_block_bitmap() can be:
bit_max += ext4_bg_num_gdb(sb, block_group, 1);
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-06-16 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 14:24 [PATCH] ext4: fix ext4_init_block_bitmap() for metablock block group Akinobu Mita
2008-06-16 5:19 ` Andreas Dilger [this message]
2008-06-16 14:10 ` Akinobu Mita
2008-06-16 19:19 ` Andreas Dilger
2008-06-16 23:57 ` Mingming
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=20080616051859.GK3726@webber.adilger.int \
--to=adilger@sun.com \
--cc=adilger@clusterfs.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.com \
--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