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 v4 09/13] locks: don't reference original flock struct in F_GETLK handlers
Date: Thu, 19 Dec 2013 08:34:21 -0500 [thread overview]
Message-ID: <1387460065-28269-10-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1387460065-28269-1-git-send-email-jlayton@redhat.com>
The locks code currently sanity checks the type values in the flock
struct before doing the flock->file_lock conversion. That will be
problematic when new l_type values are introduced in a later patch.
Instead, do the flock_to_posix_lock conversion first, and then sanity
check the values in the file_lock instead.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
fs/locks.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index 820322d..8180141 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1905,14 +1905,15 @@ int fcntl_getlk(struct file *filp, struct flock __user *l)
error = -EFAULT;
if (copy_from_user(&flock, l, sizeof(flock)))
goto out;
- error = -EINVAL;
- if ((flock.l_type != F_RDLCK) && (flock.l_type != F_WRLCK))
- goto out;
error = flock_to_posix_lock(filp, &file_lock, &flock);
if (error)
goto out;
+ error = -EINVAL;
+ if ((file_lock.fl_type != F_RDLCK) && (file_lock.fl_type != F_WRLCK))
+ goto out;
+
error = vfs_test_lock(filp, &file_lock);
if (error)
goto out;
@@ -2073,14 +2074,15 @@ int fcntl_getlk64(struct file *filp, struct flock64 __user *l)
error = -EFAULT;
if (copy_from_user(&flock, l, sizeof(flock)))
goto out;
- error = -EINVAL;
- if ((flock.l_type != F_RDLCK) && (flock.l_type != F_WRLCK))
- goto out;
error = flock64_to_posix_lock(filp, &file_lock, &flock);
if (error)
goto out;
+ error = -EINVAL;
+ if ((file_lock.fl_type != F_RDLCK) && (file_lock.fl_type != F_WRLCK))
+ goto out;
+
error = vfs_test_lock(filp, &file_lock);
if (error)
goto out;
--
1.8.4.2
next prev parent reply other threads:[~2013-12-19 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 13:34 [PATCH v4 00/13] locks: implement "filp-private" (aka UNPOSIX) locks Jeff Layton
2013-12-19 13:34 ` [PATCH v4 01/13] locks: close potential race between setlease and open Jeff Layton
2013-12-19 13:34 ` [PATCH v4 02/13] locks: clean up comment typo Jeff Layton
2013-12-19 13:34 ` [PATCH v4 03/13] locks: remove "inline" qualifier from fl_link manipulation functions Jeff Layton
2013-12-19 13:34 ` [PATCH v4 04/13] locks: add __acquires and __releases annotations to locks_start and locks_stop Jeff Layton
2013-12-19 13:34 ` [PATCH v4 05/13] locks: eliminate BUG() call when there's an unexpected lock on file close Jeff Layton
2013-12-19 13:34 ` [PATCH v4 06/13] locks: consolidate common code in the flock_to_posix_lock routines Jeff Layton
2013-12-19 13:34 ` [PATCH v4 07/13] locks: simplify overflow checking Jeff Layton
2013-12-19 13:34 ` [PATCH v4 08/13] locks: consolidate checks for compatible filp->f_mode values in setlk handlers Jeff Layton
2013-12-19 13:34 ` Jeff Layton [this message]
2013-12-19 13:34 ` [PATCH v4 10/13] locks: rename locks_remove_flock to locks_remove_file Jeff Layton
2013-12-19 13:34 ` [PATCH v4 11/13] locks: show private lock types in /proc/locks Jeff Layton
2013-12-19 13:34 ` [PATCH v4 12/13] locks: report l_pid as -1 for FL_FILE_PVT locks Jeff Layton
2013-12-19 13:34 ` [PATCH v4 13/13] locks: add new "private" lock type that is owned by the filp Jeff Layton
2013-12-19 13:52 ` [PATCH v4 00/13] locks: implement "filp-private" (aka UNPOSIX) locks Scott Lovenberg
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=1387460065-28269-10-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).