From: Jeff Layton <jeff.layton@primarydata.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
"J. Bruce Fields" <bfields@fieldses.org>,
Christoph Hellwig <hch@lst.de>,
Dave Chinner <david@fromorbit.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: [PATCH 0/4] locks: flock and lease related bugfixes, and remove i_flctx counters
Date: Tue, 17 Feb 2015 07:46:26 -0500 [thread overview]
Message-ID: <1424177190-14252-1-git-send-email-jeff.layton@primarydata.com> (raw)
This patchset should fix the problems that Linus spotted in the flock
code yesterday, as well as another bug in the lease code that I spotted
while patching those up.
It'll be interesting to see if this fixes the problem that Kirill
reported yesterday. If these looks acceptable, then I can send another
pull request or you can just use the one below.
------------------------[snip]----------------------------------
The following changes since commit 1fa185ebcbcefdc5229c783450c9f0439a69f0c1:
Merge tag 'cris-for-3.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris (2015-02-15 18:02:02 -0800)
are available in the git repository at:
git://git.samba.org/jlayton/linux.git tags/locks-v3.20-2
for you to fetch changes up to c07ef59a2e7f768ec39fb9c93419e27d09698e22:
locks: only remove leases associated with the file being closed (2015-02-17 06:59:42 -0500)
Jeff Layton (4):
Revert "locks: keep a count of locks on the flctx lists"
locks: remove conditional lock release in middle of flock_lock_file
locks: when upgrading, don't remove old flock lock until replacing
with new one
locks: only remove leases associated with the file being closed
fs/ceph/locks.c | 11 ++++++--
fs/cifs/file.c | 14 +++++++---
fs/locks.c | 78 ++++++++++++++++++++++++------------------------------
include/linux/fs.h | 3 ---
4 files changed, 53 insertions(+), 53 deletions(-)
--
2.1.0
next reply other threads:[~2015-02-17 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 12:46 Jeff Layton [this message]
2015-02-17 12:46 ` [PATCH 1/4] Revert "locks: keep a count of locks on the flctx lists" Jeff Layton
2015-02-17 12:46 ` [PATCH 2/4] locks: remove conditional lock release in middle of flock_lock_file Jeff Layton
2015-02-17 17:10 ` J. Bruce Fields
2015-02-17 17:56 ` Jeff Layton
2015-02-17 19:11 ` J. Bruce Fields
2015-02-17 22:21 ` J. Bruce Fields
2015-02-17 22:29 ` Jeff Layton
2015-02-17 12:46 ` [PATCH 3/4] locks: when upgrading, don't remove old flock lock until replacing with new one Jeff Layton
2015-02-17 12:46 ` [PATCH 4/4] locks: only remove leases associated with the file being closed Jeff Layton
2015-02-17 19:55 ` [PATCH 0/4] locks: flock and lease related bugfixes, and remove i_flctx counters Linus Torvalds
2015-02-17 20:20 ` Linus Torvalds
2015-02-17 20:20 ` Al Viro
2015-02-17 21:10 ` 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=1424177190-14252-1-git-send-email-jeff.layton@primarydata.com \
--to=jeff.layton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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).