linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dai Ngo <dai.ngo@oracle.com>
To: chuck.lever@oracle.com, bfields@fieldses.org
Cc: jlayton@redhat.com, viro@zeniv.linux.org.uk,
	linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH RFC v13 3/4] fs/lock: only call lm_breaker_owns_lease if there is conflict.
Date: Sat, 12 Feb 2022 10:12:54 -0800	[thread overview]
Message-ID: <1644689575-1235-4-git-send-email-dai.ngo@oracle.com> (raw)
In-Reply-To: <1644689575-1235-1-git-send-email-dai.ngo@oracle.com>

Modify leases_conflict to call lm_breaker_owns_lease only if
there is real conflict.  This is to allow the lock manager to
resolve the conflict if possible.

Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
---
 fs/locks.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/locks.c b/fs/locks.c
index 52ede42651df..050acf8b5110 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1387,9 +1387,6 @@ static bool leases_conflict(struct file_lock *lease, struct file_lock *breaker)
 {
 	bool rc;
 
-	if (lease->fl_lmops->lm_breaker_owns_lease
-			&& lease->fl_lmops->lm_breaker_owns_lease(lease))
-		return false;
 	if ((breaker->fl_flags & FL_LAYOUT) != (lease->fl_flags & FL_LAYOUT)) {
 		rc = false;
 		goto trace;
@@ -1400,6 +1397,9 @@ static bool leases_conflict(struct file_lock *lease, struct file_lock *breaker)
 	}
 
 	rc = locks_conflict(breaker, lease);
+	if (rc && lease->fl_lmops->lm_breaker_owns_lease &&
+		lease->fl_lmops->lm_breaker_owns_lease(lease))
+		rc = false;
 trace:
 	trace_leases_conflict(rc, lease, breaker);
 	return rc;
-- 
2.9.5


  parent reply	other threads:[~2022-02-12 18:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 18:12 [PATCH RFC v13 0/4] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-02-12 18:12 ` [PATCH RFC v13 1/4] fs/lock: documentation cleanup. Replace inode->i_lock with flc_lock Dai Ngo
2022-02-14 17:03   ` Chuck Lever III
2022-02-14 17:24     ` Jeff Layton
2022-02-12 18:12 ` [PATCH RFC v13 2/4] fs/lock: add new callback, lm_lock_expired, to lock_manager_operations Dai Ngo
2022-02-12 18:12 ` Dai Ngo [this message]
2022-02-12 18:12 ` [PATCH RFC v13 4/4] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-02-15 17:17   ` Chuck Lever III
2022-02-16  9:56     ` dai.ngo
2022-02-16 16:15       ` Chuck Lever III
2022-02-18 18:03         ` dai.ngo
2022-02-18 18:28           ` Chuck Lever III

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=1644689575-1235-4-git-send-email-dai.ngo@oracle.com \
    --to=dai.ngo@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).