From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] GFS2: return conflicts for GETLK
Date: Sat, 09 Jun 2007 15:33:45 +0100 [thread overview]
Message-ID: <1181399625.25918.281.camel@quoit> (raw)
In-Reply-To: <20070608220140.GO31758@redhat.com>
Hi,
Now added to the GFS2 -nmw git tree. Thanks,
Steve.
On Fri, 2007-06-08 at 17:01 -0500, David Teigland wrote:
> We weren't returning the correct result when GETLK found a conflict,
> which is indicated by userspace passing back a 1.
> (Typo in the previous post of this patch.)
>
> Signed-off-by: Abhijith Das <adas redhat com>
> Signed-off-by: David Teigland <teigland redhat com>
>
> Index: linux-quilt/fs/gfs2/locking/dlm/plock.c
> ===================================================================
> --- linux-quilt.orig/fs/gfs2/locking/dlm/plock.c 2007-06-08 15:26:03.000000000 -0500
> +++ linux-quilt/fs/gfs2/locking/dlm/plock.c 2007-06-08 16:59:54.000000000 -0500
> @@ -254,16 +254,20 @@
> }
> spin_unlock(&ops_lock);
>
> + /* info.rv from userspace is 1 for conflict, 0 for no-conflict,
> + -ENOENT if there are no locks on the file */
> +
> rv = op->info.rv;
>
> fl->fl_type = F_UNLCK;
> if (rv == -ENOENT)
> rv = 0;
> - else if (rv == 0 && op->info.pid != fl->fl_pid) {
> + else if (rv > 0) {
> fl->fl_type = (op->info.ex) ? F_WRLCK : F_RDLCK;
> fl->fl_pid = op->info.pid;
> fl->fl_start = op->info.start;
> fl->fl_end = op->info.end;
> + rv = 0;
> }
>
> kfree(op);
prev parent reply other threads:[~2007-06-09 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 21:51 [Cluster-devel] [PATCH] GFS2: return conflicts for GETLK David Teigland
2007-06-08 22:01 ` David Teigland
2007-06-09 14:33 ` 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=1181399625.25918.281.camel@quoit \
--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).