All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: Fix kernel BUG at fs/ext4/mballoc.c:910!
Date: Thu, 14 Feb 2008 13:48:21 +0100	[thread overview]
Message-ID: <47B43895.7040709@bull.net> (raw)
In-Reply-To: <20080214041300.GA7835@skywalker>

Aneesh Kumar K.V wrote:
>>> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
>>> index b0f84b4..0275150 100644
>>> --- a/fs/ext4/mballoc.c
>>> +++ b/fs/ext4/mballoc.c
>>> @@ -907,7 +907,7 @@ static void ext4_mb_mark_free_simple(struct super_block *sb,
>>>  	unsigned short chunk;
>>>  	unsigned short border;
>>>  
>>> -	BUG_ON(len >= EXT4_BLOCKS_PER_GROUP(sb));
>>> +	BUG_ON(len > EXT4_BLOCKS_PER_GROUP(sb));
>>>  
>>>  	border = 2 << sb->s_blocksize_bits;
>>>  
>>> @@ -3286,7 +3286,7 @@ static void ext4_mb_normalize_request(struct ext4_allocation_context *ac,
>>>  	}
>>>  	BUG_ON(start + size <= ac->ac_o_ex.fe_logical &&
>>>  			start > ac->ac_o_ex.fe_logical);
>>> -	BUG_ON(size <= 0 || size >= EXT4_BLOCKS_PER_GROUP(ac->ac_sb));
>>> +	BUG_ON(size <= 0 || size > EXT4_BLOCKS_PER_GROUP(ac->ac_sb));
> 
> I am not sure about this. Here size is the normalized request len. 
> Did we hit this BUG_ON ?
In fact, no. So, I'll not make the change now.
Thanks for your response and your explanations.
    Valerie

  reply	other threads:[~2008-02-14 12:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 17:19 [PATCH] ext4: Fix kernel BUG at fs/ext4/mballoc.c:910! Valerie Clement
2008-02-13 20:33 ` Andreas Dilger
2008-02-14  4:13   ` Aneesh Kumar K.V
2008-02-14 12:48     ` Valerie Clement [this message]
2008-02-14 12:34   ` Valerie Clement

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=47B43895.7040709@bull.net \
    --to=valerie.clement@bull.net \
    --cc=aneesh.kumar@linux.vnet.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.