From: Jeff Layton <jlayton@kernel.org>
To: Jann Horn <jannh@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Chuck Lever <chuck.lever@oracle.com>,
Alexander Aring <alex.aring@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH] filelock: Fix fcntl/close race recovery compat path
Date: Tue, 23 Jul 2024 11:50:37 -0400 [thread overview]
Message-ID: <0616b6be151e2063627fb7f22100b9d3407aceb3.camel@kernel.org> (raw)
In-Reply-To: <20240723-fs-lock-recover-compatfix-v1-1-148096719529@google.com>
On Tue, 2024-07-23 at 17:03 +0200, Jann Horn wrote:
> When I wrote commit 3cad1bc01041 ("filelock: Remove locks reliably when
> fcntl/close race is detected"), I missed that there are two copies of the
> code I was patching: The normal version, and the version for 64-bit offsets
> on 32-bit kernels.
> Thanks to Greg KH for stumbling over this while doing the stable
> backport...
>
> Apply exactly the same fix to the compat path for 32-bit kernels.
>
> Fixes: c293621bbf67 ("[PATCH] stale POSIX lock handling")
> Cc: stable@kernel.org
> Link: https://bugs.chromium.org/p/project-zero/issues/detail?id=2563
> Signed-off-by: Jann Horn <jannh@google.com>
> ---
> fs/locks.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/fs/locks.c b/fs/locks.c
> index bdd94c32256f..9afb16e0683f 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -2570,8 +2570,9 @@ int fcntl_setlk64(unsigned int fd, struct file *filp, unsigned int cmd,
> error = do_lock_file_wait(filp, cmd, file_lock);
>
> /*
> - * Attempt to detect a close/fcntl race and recover by releasing the
> - * lock that was just acquired. There is no need to do that when we're
> + * Detect close/fcntl races and recover by zapping all POSIX locks
> + * associated with this file and our files_struct, just like on
> + * filp_flush(). There is no need to do that when we're
> * unlocking though, or for OFD locks.
> */
> if (!error && file_lock->c.flc_type != F_UNLCK &&
> @@ -2586,9 +2587,7 @@ int fcntl_setlk64(unsigned int fd, struct file *filp, unsigned int cmd,
> f = files_lookup_fd_locked(files, fd);
> spin_unlock(&files->file_lock);
> if (f != filp) {
> - file_lock->c.flc_type = F_UNLCK;
> - error = do_lock_file_wait(filp, cmd, file_lock);
> - WARN_ON_ONCE(error);
> + locks_remove_posix(filp, files);
> error = -EBADF;
> }
> }
>
> ---
> base-commit: 66ebbdfdeb093e097399b1883390079cd4c3022b
> change-id: 20240723-fs-lock-recover-compatfix-cf2cbab343d1
Doh! Good catch.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-07-23 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 15:03 [PATCH] filelock: Fix fcntl/close race recovery compat path Jann Horn
2024-07-23 15:41 ` Christian Brauner
2024-07-23 15:50 ` Jeff Layton [this message]
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=0616b6be151e2063627fb7f22100b9d3407aceb3.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=alex.aring@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).