From: Jeff Layton <jlayton@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: nfs-ganesha-devel@lists.sourceforge.net,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 13/14] locks: skip deadlock detection on FL_FILE_PVT locks
Date: Tue, 14 Jan 2014 14:06:53 -0500 [thread overview]
Message-ID: <1389726414-30990-14-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1389726414-30990-1-git-send-email-jlayton@redhat.com>
It's not really feasible to do deadlock detection with FL_FILE_PVT
locks since they aren't owned by a single task, per-se. Deadlock
detection also tends to be rather expensive so just skip it for
these sorts of locks.
Also, add a FIXME comment about adding more limited deadlock detection
that just applies to ro -> rw upgrades, per Andy's request.
Cc: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
fs/locks.c | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index f8cd6d7..8c5bc07 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -564,7 +564,7 @@ static void __locks_insert_block(struct file_lock *blocker,
BUG_ON(!list_empty(&waiter->fl_block));
waiter->fl_next = blocker;
list_add_tail(&waiter->fl_block, &blocker->fl_block);
- if (IS_POSIX(blocker))
+ if (IS_POSIX(blocker) && !IS_FILE_PVT(blocker))
locks_insert_global_blocked(waiter);
}
@@ -757,8 +757,16 @@ EXPORT_SYMBOL(posix_test_lock);
* Note: the above assumption may not be true when handling lock
* requests from a broken NFS client. It may also fail in the presence
* of tasks (such as posix threads) sharing the same open file table.
- *
* To handle those cases, we just bail out after a few iterations.
+ *
+ * For FL_FILE_PVT locks, the owner is the filp, not the files_struct.
+ * Because the owner is not even nominally tied to a thread of
+ * execution, the deadlock detection below can't reasonably work well. Just
+ * skip it for those.
+ *
+ * In principle, we could do a more limited deadlock detection on FL_FILE_PVT
+ * locks that just checks for the case where two tasks are attempting to
+ * upgrade from read to write locks on the same inode.
*/
#define MAX_DEADLK_ITERATIONS 10
@@ -781,6 +789,13 @@ static int posix_locks_deadlock(struct file_lock *caller_fl,
{
int i = 0;
+ /*
+ * This deadlock detector can't reasonably detect deadlocks with
+ * FL_FILE_PVT locks, since they aren't owned by a process, per-se.
+ */
+ if (IS_FILE_PVT(caller_fl))
+ return 0;
+
while ((block_fl = what_owner_is_waiting_for(block_fl))) {
if (i++ > MAX_DEADLK_ITERATIONS)
return 0;
--
1.8.4.2
next prev parent reply other threads:[~2014-01-14 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:06 [PATCH v6 00/14] locks: implement "file-private" (aka UNPOSIX) locks Jeff Layton
2014-01-14 19:06 ` [PATCH v6 01/14] locks: close potential race between setlease and open Jeff Layton
2014-01-14 19:06 ` [PATCH v6 02/14] locks: clean up comment typo Jeff Layton
2014-01-14 19:06 ` [PATCH v6 03/14] locks: remove "inline" qualifier from fl_link manipulation functions Jeff Layton
2014-01-14 19:06 ` [PATCH v6 04/14] locks: add __acquires and __releases annotations to locks_start and locks_stop Jeff Layton
2014-01-14 19:06 ` [PATCH v6 05/14] locks: eliminate BUG() call when there's an unexpected lock on file close Jeff Layton
2014-01-14 19:06 ` [PATCH v6 06/14] locks: fix posix lock range overflow handling Jeff Layton
2014-01-14 19:06 ` [PATCH v6 07/14] locks: consolidate checks for compatible filp->f_mode values in setlk handlers Jeff Layton
2014-01-14 19:06 ` [PATCH v6 08/14] MAINTAINERS: add Bruce and myself to list of maintainers for file locking code Jeff Layton
2014-01-14 19:06 ` [PATCH v6 09/14] locks: rename locks_remove_flock to locks_remove_file Jeff Layton
2014-01-14 19:06 ` [PATCH v6 10/14] locks: make /proc/locks show IS_FILE_PVT locks with a P suffix Jeff Layton
2014-01-14 19:06 ` [PATCH v6 11/14] locks: report l_pid as -1 for FL_FILE_PVT locks Jeff Layton
2014-01-14 19:06 ` [PATCH v6 12/14] locks: pass the cmd value to fcntl_getlk/getlk64 Jeff Layton
2014-01-14 19:06 ` Jeff Layton [this message]
2014-01-14 19:06 ` [PATCH v6 14/14] locks: add new fcntl cmd values for handling file private locks Jeff Layton
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=1389726414-30990-14-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.org \
/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).