From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: fix recursive locking during rindex truncates
Date: Tue, 30 Nov 2010 16:05:32 +0000 [thread overview]
Message-ID: <1291133132.2448.15.camel@dolmen> (raw)
In-Reply-To: <20101124055255.GM13763@ether.msp.redhat.com>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Tue, 2010-11-23 at 23:52 -0600, Benjamin Marzinski wrote:
> When you truncate the rindex file, you need to avoid calling gfs2_rindex_hold,
> since you already hold it. However, if you haven't already read in the
> resource groups, you need to do that.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> fs/gfs2/bmap.c | 9 +++++++--
> fs/gfs2/rgrp.c | 2 +-
> fs/gfs2/rgrp.h | 1 +
> 3 files changed, 9 insertions(+), 3 deletions(-)
>
> Index: gfs2-2.6-nmw/fs/gfs2/bmap.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/bmap.c
> +++ gfs2-2.6-nmw/fs/gfs2/bmap.c
> @@ -780,7 +780,11 @@ static int do_strip(struct gfs2_inode *i
> if (metadata)
> revokes = (height) ? sdp->sd_inptrs : sdp->sd_diptrs;
>
> - error = gfs2_rindex_hold(sdp, &ip->i_alloc->al_ri_gh);
> + if (ip != GFS2_I(sdp->sd_rindex))
> + error = gfs2_rindex_hold(sdp, &ip->i_alloc->al_ri_gh);
> + else if (!sdp->sd_rgrps)
> + error = gfs2_ri_update(ip);
> +
> if (error)
> return error;
>
> @@ -879,7 +883,8 @@ out_rg_gunlock:
> out_rlist:
> gfs2_rlist_free(&rlist);
> out:
> - gfs2_glock_dq_uninit(&ip->i_alloc->al_ri_gh);
> + if (ip != GFS2_I(sdp->sd_rindex))
> + gfs2_glock_dq_uninit(&ip->i_alloc->al_ri_gh);
> return error;
> }
>
> Index: gfs2-2.6-nmw/fs/gfs2/rgrp.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/rgrp.c
> +++ gfs2-2.6-nmw/fs/gfs2/rgrp.c
> @@ -583,7 +583,7 @@ static int read_rindex_entry(struct gfs2
> * Returns: 0 on successful update, error code otherwise
> */
>
> -static int gfs2_ri_update(struct gfs2_inode *ip)
> +int gfs2_ri_update(struct gfs2_inode *ip)
> {
> struct gfs2_sbd *sdp = GFS2_SB(&ip->i_inode);
> struct inode *inode = &ip->i_inode;
> Index: gfs2-2.6-nmw/fs/gfs2/rgrp.h
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/rgrp.h
> +++ gfs2-2.6-nmw/fs/gfs2/rgrp.h
> @@ -46,6 +46,7 @@ gfs2_inplace_reserve_i((ip), __FILE__, _
>
> extern void gfs2_inplace_release(struct gfs2_inode *ip);
>
> +extern int gfs2_ri_update(struct gfs2_inode *ip);
> extern int gfs2_alloc_block(struct gfs2_inode *ip, u64 *bn, unsigned int *n);
> extern int gfs2_alloc_di(struct gfs2_inode *ip, u64 *bn, u64 *generation);
>
>
prev parent reply other threads:[~2010-11-30 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 5:52 [Cluster-devel] [PATCH] GFS2: fix recursive locking during rindex truncates Benjamin Marzinski
2010-11-30 16:05 ` 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=1291133132.2448.15.camel@dolmen \
--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.