public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming <cmm@us.ibm.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Tweedie <sct@redhat.com>,
	adilger@clusterfs.com, Theodore Tso <tytso@MIT.EDU>
Subject: Re: [PATCH] ext4: fix ext4_init_block_bitmap() for metablock block group
Date: Mon, 16 Jun 2008 16:57:01 -0700	[thread overview]
Message-ID: <1213660621.27507.50.camel@BVR-FS.beaverton.ibm.com> (raw)
In-Reply-To: <20080616191902.GU3726@webber.adilger.int>


On Mon, 2008-06-16 at 13:19 -0600, Andreas Dilger wrote:
> On Jun 16, 2008  23:10 +0900, Akinobu Mita wrote:
> > Looks good to me. But I'd like to divide into the change into simple
> > bugfix and cleanup patch in order to clarify the each change.
> > 
> > Here is a bugfix only patch.
> > 
> > From: Akinobu Mita <akinobu.mita@gmail.com>
> > Subject: ext4: fix ext4_init_block_bitmap() for metablock block group
> > 
> > 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)
> > 
> > group_rel in the original code should be calculated by:
> > 
> >         group_rel = block_group % EXT4_DESC_PER_BLOCK(sb);
> > 
> > No need to subtract s_first_meta_bg from brock_group.
> > It will be equivalent what ext4_bg_num_gdb_meta() does
> > 
> > Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Stephen Tweedie <sct@redhat.com>
> > Cc: adilger@clusterfs.com
> > Cc: Mingming Cao <cmm@us.ibm.com>
> > Cc: Theodore Tso <tytso@MIT.EDU>
> 
> Acked-by: Andreas Dilger <adilger@sun.com>
> 

FYI, I have added this patch to patch queue

Mingming
> > ---
> >  fs/ext4/balloc.c |    5 ++---
> >  1 file changed, 2 insertions(+), 3 deletions(-)
> > 
> > Index: 2.6-git/fs/ext4/balloc.c
> > ===================================================================
> > --- 2.6-git.orig/fs/ext4/balloc.c
> > +++ 2.6-git/fs/ext4/balloc.c
> > @@ -121,9 +121,8 @@ unsigned ext4_init_block_bitmap(struct s
> >  				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);
> > +		int group_rel = block_group % EXT4_DESC_PER_BLOCK(sb);
> > +
> >  		if (group_rel == 0 || group_rel == 1 ||
> >  		    (group_rel == EXT4_DESC_PER_BLOCK(sb) - 1))
> >  			bit_max += 1;
> 
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
> 


      reply	other threads:[~2008-06-16 23:56 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
2008-06-16 14:10   ` Akinobu Mita
2008-06-16 19:19     ` Andreas Dilger
2008-06-16 23:57       ` Mingming [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=1213660621.27507.50.camel@BVR-FS.beaverton.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=adilger@sun.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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