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 07/14] locks: consolidate checks for compatible filp->f_mode values in setlk handlers
Date: Tue, 14 Jan 2014 14:06:47 -0500 [thread overview]
Message-ID: <1389726414-30990-8-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1389726414-30990-1-git-send-email-jlayton@redhat.com>
Move this check into flock64_to_posix_lock instead of duplicating it in
two places. This also fixes a minor wart in the code where we continue
referring to the struct flock after converting it to struct file_lock.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
fs/locks.c | 46 ++++++++++++----------------------------------
1 file changed, 12 insertions(+), 34 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index b49e853..4cd2578 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -388,6 +388,18 @@ static int flock64_to_posix_lock(struct file *filp, struct file_lock *fl,
fl->fl_ops = NULL;
fl->fl_lmops = NULL;
+ /* Ensure that fl->fl_filp has compatible f_mode */
+ switch (l->l_type) {
+ case F_RDLCK:
+ if (!(filp->f_mode & FMODE_READ))
+ return -EBADF;
+ break;
+ case F_WRLCK:
+ if (!(filp->f_mode & FMODE_WRITE))
+ return -EBADF;
+ break;
+ }
+
return assign_type(fl, l->l_type);
}
@@ -2025,23 +2037,6 @@ again:
file_lock->fl_flags |= FL_SLEEP;
}
- error = -EBADF;
- switch (flock.l_type) {
- case F_RDLCK:
- if (!(filp->f_mode & FMODE_READ))
- goto out;
- break;
- case F_WRLCK:
- if (!(filp->f_mode & FMODE_WRITE))
- goto out;
- break;
- case F_UNLCK:
- break;
- default:
- error = -EINVAL;
- goto out;
- }
-
error = do_lock_file_wait(filp, cmd, file_lock);
/*
@@ -2143,23 +2138,6 @@ again:
file_lock->fl_flags |= FL_SLEEP;
}
- error = -EBADF;
- switch (flock.l_type) {
- case F_RDLCK:
- if (!(filp->f_mode & FMODE_READ))
- goto out;
- break;
- case F_WRLCK:
- if (!(filp->f_mode & FMODE_WRITE))
- goto out;
- break;
- case F_UNLCK:
- break;
- default:
- error = -EINVAL;
- goto out;
- }
-
error = do_lock_file_wait(filp, cmd, file_lock);
/*
--
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 ` Jeff Layton [this message]
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 ` [PATCH v6 13/14] locks: skip deadlock detection on FL_FILE_PVT locks Jeff Layton
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-8-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).