From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH v2 1/6] locks: fix unlock when fcntl_setlk races with a close
Date: Fri, 8 Jan 2016 10:55:33 -0500 [thread overview]
Message-ID: <20160108155533.GA3426@fieldses.org> (raw)
In-Reply-To: <1452261014-1682-2-git-send-email-jeff.layton@primarydata.com>
On Fri, Jan 08, 2016 at 08:50:09AM -0500, Jeff Layton wrote:
> Dmitry reported that he was able to reproduce the WARN_ON_ONCE that
> fires in locks_free_lock_context when the flc_posix list isn't empty.
>
> The problem turns out to be that we're basically rebuilding the
> file_lock from scratch in fcntl_setlk when we discover that the setlk
> has raced with a close. If the l_whence field is SEEK_CUR or SEEK_END,
> then we may end up with fl_start and fl_end values that differ from
> when the lock was initially set, if the file position or length of the
> file has changed in the interim.
>
> Fix this by just reusing the same lock request structure, and simply
> override fl_type value with F_UNLCK as appropriate. That ensures that
> we really are unlocking the lock that was initially set.
You could also just do a whole-file unlock, couldn't you? That would
seem less confusing to me. But maybe I'm missing something.
--b.
>
> While we're there, make sure that we do pop a WARN_ON_ONCE if the
> removal ever fails. Also return -EBADF in this event, since that's
> what we would have returned if the close had happened earlier.
>
> Cc: "J. Bruce Fields" <bfields@fieldses.org>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: <stable@vger.kernel.org>
> Fixes: c293621bbf67 (stale POSIX lock handling)
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
> ---
> fs/locks.c | 51 ++++++++++++++++++++++++++++++---------------------
> 1 file changed, 30 insertions(+), 21 deletions(-)
>
> diff --git a/fs/locks.c b/fs/locks.c
> index 593dca300b29..c263aff793bc 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -2181,7 +2181,6 @@ int fcntl_setlk(unsigned int fd, struct file *filp, unsigned int cmd,
> goto out;
> }
>
> -again:
> error = flock_to_posix_lock(filp, file_lock, &flock);
> if (error)
> goto out;
> @@ -2223,19 +2222,22 @@ again:
> * Attempt to detect a close/fcntl race and recover by
> * releasing the lock that was just acquired.
> */
> - /*
> - * we need that spin_lock here - it prevents reordering between
> - * update of i_flctx->flc_posix and check for it done in close().
> - * rcu_read_lock() wouldn't do.
> - */
> - spin_lock(¤t->files->file_lock);
> - f = fcheck(fd);
> - spin_unlock(¤t->files->file_lock);
> - if (!error && f != filp && flock.l_type != F_UNLCK) {
> - flock.l_type = F_UNLCK;
> - goto again;
> + if (!error && file_lock->fl_type != F_UNLCK) {
> + /*
> + * We need that spin_lock here - it prevents reordering between
> + * update of i_flctx->flc_posix and check for it done in
> + * close(). rcu_read_lock() wouldn't do.
> + */
> + spin_lock(¤t->files->file_lock);
> + f = fcheck(fd);
> + spin_unlock(¤t->files->file_lock);
> + if (f != filp) {
> + file_lock->fl_type = F_UNLCK;
> + error = do_lock_file_wait(filp, cmd, file_lock);
> + WARN_ON_ONCE(error);
> + error = -EBADF;
> + }
> }
> -
> out:
> locks_free_lock(file_lock);
> return error;
> @@ -2321,7 +2323,6 @@ int fcntl_setlk64(unsigned int fd, struct file *filp, unsigned int cmd,
> goto out;
> }
>
> -again:
> error = flock64_to_posix_lock(filp, file_lock, &flock);
> if (error)
> goto out;
> @@ -2363,14 +2364,22 @@ again:
> * Attempt to detect a close/fcntl race and recover by
> * releasing the lock that was just acquired.
> */
> - spin_lock(¤t->files->file_lock);
> - f = fcheck(fd);
> - spin_unlock(¤t->files->file_lock);
> - if (!error && f != filp && flock.l_type != F_UNLCK) {
> - flock.l_type = F_UNLCK;
> - goto again;
> + if (!error && file_lock->fl_type != F_UNLCK) {
> + /*
> + * We need that spin_lock here - it prevents reordering between
> + * update of i_flctx->flc_posix and check for it done in
> + * close(). rcu_read_lock() wouldn't do.
> + */
> + spin_lock(¤t->files->file_lock);
> + f = fcheck(fd);
> + spin_unlock(¤t->files->file_lock);
> + if (f != filp) {
> + file_lock->fl_type = F_UNLCK;
> + error = do_lock_file_wait(filp, cmd, file_lock);
> + WARN_ON_ONCE(error);
> + error = -EBADF;
> + }
> }
> -
> out:
> locks_free_lock(file_lock);
> return error;
> --
> 2.5.0
next prev parent reply other threads:[~2016-01-08 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:37 fs: WARNING in locks_free_lock_context() Dmitry Vyukov
2015-12-23 13:54 ` Jeff Layton
2016-02-03 18:19 ` William Dauchy
2016-02-03 18:26 ` Jeff Layton
2016-02-03 18:28 ` William Dauchy
2016-01-08 2:22 ` [PATCH] locks: fix unlock when fcntl_setlk races with a close Jeff Layton
2016-01-08 12:48 ` Jeff Layton
2016-01-08 16:16 ` J. Bruce Fields
2016-01-08 13:50 ` [PATCH v2 0/6] locks: better debugging and fix for setlk/close race handling Jeff Layton
2016-01-08 13:50 ` [PATCH v2 1/6] locks: fix unlock when fcntl_setlk races with a close Jeff Layton
2016-01-08 15:55 ` J. Bruce Fields [this message]
2016-01-08 16:11 ` Jeff Layton
2016-01-08 16:21 ` J. Bruce Fields
2016-01-08 16:22 ` J. Bruce Fields
2016-01-08 16:26 ` J. Bruce Fields
2016-01-08 13:50 ` [PATCH v2 2/6] locks: don't check for race with close when setting OFD lock Jeff Layton
2016-01-08 13:50 ` [PATCH v2 3/6] locks: sprinkle some tracepoints around the file locking code Jeff Layton
2016-01-08 13:50 ` [PATCH v2 4/6] locks: pass inode pointer to locks_free_lock_context Jeff Layton
2016-01-08 13:50 ` [PATCH v2 5/6] locks: prink more detail when there are leaked locks Jeff Layton
2016-01-08 13:50 ` [PATCH v2 6/6] locks: rename __posix_lock_file to posix_lock_inode 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=20160108155533.GA3426@fieldses.org \
--to=bfields@fieldses.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=jlayton@poochiereds.net \
--cc=kcc@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--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).