cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] Unlock rindex mutex on glock error
Date: Thu, 01 Mar 2012 10:23:18 +0000	[thread overview]
Message-ID: <1330597398.2704.16.camel@menhir> (raw)
In-Reply-To: <af43e4a6-37ab-4939-ae52-6ba601f9014c@zmail12.collab.prod.int.phx2.redhat.com>

Hi,

Now in the -nmw git tree. Thanks,

Steve.

On Wed, 2012-02-29 at 15:15 -0500, Bob Peterson wrote:
> Hi,
> 
> This patch fixes an error path in function gfs2_rindex_update
> that leaves the rindex mutex held.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> --
>  fs/gfs2/rgrp.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 1446b4e..e09370e 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -699,13 +699,14 @@ int gfs2_rindex_update(struct gfs2_sbd *sdp)
>  		if (!gfs2_glock_is_locked_by_me(gl)) {
>  			error = gfs2_glock_nq_init(gl, LM_ST_SHARED, 0, &ri_gh);
>  			if (error)
> -				return error;
> +				goto out_unlock;
>  			unlock_required = 1;
>  		}
>  		if (!sdp->sd_rindex_uptodate)
>  			error = gfs2_ri_update(ip);
>  		if (unlock_required)
>  			gfs2_glock_dq_uninit(&ri_gh);
> +out_unlock:
>  		mutex_unlock(&sdp->sd_rindex_mutex);
>  	}
>  
> 




      reply	other threads:[~2012-03-01 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12861abf-0b7d-4e06-aad9-14c0bbd06422@zmail12.collab.prod.int.phx2.redhat.com>
2012-02-29 20:15 ` [Cluster-devel] [GFS2 PATCH] Unlock rindex mutex on glock error Bob Peterson
2012-03-01 10:23   ` 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=1330597398.2704.16.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 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).