From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Jeff Layton To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Dmitry Vyukov , "J. Bruce Fields" , Alexander Viro , syzkaller , Kostya Serebryany , Alexander Potapenko , Sasha Levin , Eric Dumazet Subject: [PATCH v2 0/6] locks: better debugging and fix for setlk/close race handling Date: Fri, 8 Jan 2016 08:50:08 -0500 Message-Id: <1452261014-1682-1-git-send-email-jeff.layton@primarydata.com> In-Reply-To: <1452219742-18507-1-git-send-email-jeff.layton@primarydata.com> References: <1452219742-18507-1-git-send-email-jeff.layton@primarydata.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: The first patch in this patchset fixes a very long-standing bug in the handling of races between setlk and close. That one should be appropriate for all stable kernels and should apply to most kernels as-is. The second patch exempts OFD locks from setlk/close race handling since they shouldn't need it anyway. The rest of the patches add some better debugging for these problems and do a little function name cleanup. I'm planning to go ahead and put these into linux-next today and send them to Linus for the 4.5 merge, unless there are any objections... Jeff Layton (6): locks: fix unlock when fcntl_setlk races with a close locks: don't check for race with close when setting OFD lock locks: sprinkle some tracepoints around the file locking code locks: pass inode pointer to locks_free_lock_context locks: prink more detail when there are leaked locks locks: rename __posix_lock_file to posix_lock_inode fs/inode.c | 2 +- fs/locks.c | 123 +++++++++++++++++++++++++++------------- include/linux/fs.h | 4 +- include/trace/events/filelock.h | 77 +++++++++++++++++++++++++ 4 files changed, 165 insertions(+), 41 deletions(-) -- 2.5.0