All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Stop block extents at the end of bitmaps
Date: Tue, 28 Aug 2012 14:06:17 +0100	[thread overview]
Message-ID: <1346159177.2692.14.camel@menhir> (raw)
In-Reply-To: <1473556188.4340686.1346157956568.JavaMail.root@redhat.com>

Hi,

On Tue, 2012-08-28 at 08:45 -0400, Bob Peterson wrote:
> Hi,
> 
> This patch stops multiple block allocations if a nonzero
> return code is received from gfs2_rbm_from_block. Without
> this patch, if enough pressure is put on the file system,
> you get a kernel warning quickly followed by:
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<ffffffffa04f47e8>] gfs2_alloc_blocks+0x2c8/0x880 [gfs2]
> With this patch, things run normally.
> 
> Regards,
> 

Now in the -nmw tree. Thanks,

Steve.


> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 87ee0b7..081fba8 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -1852,8 +1852,7 @@ static void gfs2_alloc_extent(const struct gfs2_rbm *rbm, bool dinode,
>  	block++;
>  	while (*n < elen) {
>  		ret = gfs2_rbm_from_block(&pos, block);
> -		WARN_ON(ret);
> -		if (gfs2_testbit(&pos) != GFS2_BLKST_FREE)
> +		if (ret || gfs2_testbit(&pos) != GFS2_BLKST_FREE)
>  			break;
>  		gfs2_trans_add_bh(pos.rgd->rd_gl, pos.bi->bi_bh, 1);
>  		gfs2_setbit(&pos, true, GFS2_BLKST_USED);
> 




      reply	other threads:[~2012-08-28 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <593383397.4340210.1346157882093.JavaMail.root@redhat.com>
2012-08-28 12:45 ` [Cluster-devel] [GFS2 PATCH] GFS2: Stop block extents at the end of bitmaps Bob Peterson
2012-08-28 13:06   ` Steven Whitehouse [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=1346159177.2692.14.camel@menhir \
    --to=swhiteho@redhat.com \
    /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.