Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Fix problems relating to execution of files	on GFS2
Date: Mon, 07 Jan 2008 13:11:20 -0500	[thread overview]
Message-ID: <47826B48.5070109@redhat.com> (raw)
In-Reply-To: <1199726848.22038.88.camel@quoit>

Steven Whitehouse wrote:
> --- a/fs/gfs2/ops_inode.c
> +++ b/fs/gfs2/ops_inode.c
> @@ -113,8 +113,18 @@ static struct dentry *gfs2_lookup(struct inode *dir, struct dentry *dentry,
>  	if (inode && IS_ERR(inode))
>  		return ERR_PTR(PTR_ERR(inode));
>  
> -	if (inode)
> +	if (inode) {
> +		struct gfs2_glock *gl = GFS2_I(inode)->i_gl;
> +		struct gfs2_holder gh;
> +		int error;
> +		error = gfs2_glock_nq_init(gl, LM_ST_SHARED, LM_FLAG_ANY, &gh);
>   

ok, so this shared glock is now added *back*.  As I recall, its removal 
about one year ago had caused great grief in NFS portion of logic - had 
to do a tedious work to make NFS work due to this change. Now, the logic 
is reverted - has performance impact been measured (since it is a disk 
read) ?

-- Wendy
> +		if (error) {
> +			iput(inode);
> +			return ERR_PTR(error);
> +		}
> +		gfs2_glock_dq_uninit(&gh);
>  		return d_splice_alias(inode, dentry);
> +	}
>  	d_add(dentry, inode);
>  
>  	return NULL;
>
>
>   



  reply	other threads:[~2008-01-07 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 17:27 [Cluster-devel] [GFS2] Fix problems relating to execution of files on GFS2 Steven Whitehouse
2008-01-07 18:11 ` Wendy Cheng [this message]
2008-01-08  8:40   ` Steven Whitehouse

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=47826B48.5070109@redhat.com \
    --to=wcheng@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