From: Peter Staubach <staubach@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/5] ext4: unlock group before ext4_error
Date: Thu, 20 Nov 2008 13:35:11 -0500 [thread overview]
Message-ID: <4925ADDF.10103@redhat.com> (raw)
In-Reply-To: <1227205580-27596-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
> Otherwise ext4_error will cause BUG because of
> scheduling in atomic context.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> fs/ext4/mballoc.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 772e05b..039a5a6 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -460,10 +460,12 @@ static void mb_free_blocks_double(struct inode *inode, struct ext4_buddy *e4b,
> blocknr +=
> le32_to_cpu(EXT4_SB(sb)->s_es->s_first_data_block);
>
> + ext4_unlock_group(sb, e4b->bd_group);
> ext4_error(sb, __func__, "double-free of inode"
> " %lu's block %llu(bit %u in group %u)\n",
> inode ? inode->i_ino : 0, blocknr,
> first + i, e4b->bd_group);
> + ext4_unlock_group(sb, e4b->bd_group);
>
This should be ext4_lock_group(sb, e4b->bd_group); shouldn't it?
Thanx...
ps
> }
> mb_clear_bit(first + i, e4b->bd_info->bb_bitmap);
> }
> @@ -704,6 +706,7 @@ static void ext4_mb_generate_buddy(struct super_block *sb,
> grp->bb_fragments = fragments;
>
> if (free != grp->bb_free) {
> + ext4_unlock_group(sb, group);
> ext4_error(sb, __func__,
> "EXT4-fs: group %u: %u blocks in bitmap, %u in gd\n",
> group, free, grp->bb_free);
> @@ -711,6 +714,7 @@ static void ext4_mb_generate_buddy(struct super_block *sb,
> * If we intent to continue, we consider group descritor
> * corrupt and update bb_free using bitmap value
> */
> + ext4_lock_group(sb, group);
> grp->bb_free = free;
> }
>
> @@ -1625,15 +1629,18 @@ static void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac,
> * free blocks even though group info says we
> * we have free blocks
> */
> + ext4_unlock_group(sb, e4b->bd_group);
> ext4_error(sb, __func__, "%d free blocks as per "
> "group info. But bitmap says 0\n",
> free);
> + ext4_lock_group(sb, e4b->bd_group);
> break;
> }
>
> mb_find_extent(e4b, 0, i, ac->ac_g_ex.fe_len, &ex);
> BUG_ON(ex.fe_len <= 0);
> if (free < ex.fe_len) {
> + ext4_unlock_group(sb, e4b->bd_group);
> ext4_error(sb, __func__, "%d free blocks as per "
> "group info. But got %d blocks\n",
> free, ex.fe_len);
> @@ -1642,6 +1649,7 @@ static void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac,
> * indicate that the bitmap is corrupt. So exit
> * without claiming the space.
> */
> + ext4_lock_group(sb, e4b->bd_group);
> break;
> }
>
> @@ -3789,6 +3797,7 @@ ext4_mb_release_inode_pa(struct ext4_buddy *e4b, struct buffer_head *bitmap_bh,
> bit = next + 1;
> }
> if (free != pa->pa_free) {
> + ext4_unlock_group(sb, group);
> printk(KERN_CRIT "pa %p: logic %lu, phys. %lu, len %lu\n",
> pa, (unsigned long) pa->pa_lstart,
> (unsigned long) pa->pa_pstart,
> @@ -3799,6 +3808,7 @@ ext4_mb_release_inode_pa(struct ext4_buddy *e4b, struct buffer_head *bitmap_bh,
> * pa is already deleted so we use the value obtained
> * from the bitmap and continue.
> */
> + ext4_lock_group(sb, group);
> }
> atomic_add(free, &sbi->s_mb_discarded);
>
> @@ -4607,9 +4617,11 @@ ext4_mb_free_metadata(handle_t *handle, struct ext4_buddy *e4b,
> else if (block >= (entry->start_blk + entry->count))
> n = &(*n)->rb_right;
> else {
> + ext4_unlock_group(sb, e4b->bd_group);
> ext4_error(sb, __func__,
> "Double free of blocks %d (%d %d)\n",
> block, entry->start_blk, entry->count);
> + ext4_unlock_group(sb, e4b->bd_group);
> return 0;
> }
> }
>
next prev parent reply other threads:[~2008-11-20 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 18:26 [PATCH 1/5] ext4: unlock group before ext4_error Aneesh Kumar K.V
2008-11-20 18:26 ` [PATCH 3/5] ext4: Fix the race between read_block_bitmap and mark_diskspace_used Aneesh Kumar K.V
2008-11-20 18:26 ` [PATCH 4/5] ext4: Use both hi and lo bits of the group desc values Aneesh Kumar K.V
2008-11-20 18:44 ` Aneesh Kumar K.V
2008-11-20 18:34 ` [PATCH 1/5] ext4: unlock group before ext4_error Aneesh Kumar K.V
2008-11-20 18:35 ` Peter Staubach [this message]
2008-11-20 18:47 ` Aneesh Kumar K.V
2008-11-20 22:38 ` Theodore Tso
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=4925ADDF.10103@redhat.com \
--to=staubach@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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;
as well as URLs for NNTP newsgroup(s).