From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph updates for 5.12-rc1
Date: Mon, 22 Feb 2021 15:21:07 +0100 [thread overview]
Message-ID: <20210222142107.20046-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit f40ddce88593482919761f74910f42f4b84c004b:
Linux 5.11 (2021-02-14 14:32:24 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.12-rc1
for you to fetch changes up to 558b4510f622a3d96cf9d95050a04e7793d343c7:
ceph: defer flushing the capsnap if the Fb is used (2021-02-16 12:09:52 +0100)
----------------------------------------------------------------
With netfs helper library and fscache rework delayed, just a few cap
handling improvements to avoid grabbing mmap_lock in some code paths
and deal with capsnaps better and a mount option cleanup.
----------------------------------------------------------------
Ilya Dryomov (2):
libceph: deprecate [no]cephx_require_signatures options
libceph: remove osdtimeout option entirely
Jeff Layton (3):
ceph: fix flush_snap logic after putting caps
ceph: clean up inode work queueing
ceph: allow queueing cap/snap handling after putting cap references
Xiubo Li (1):
ceph: defer flushing the capsnap if the Fb is used
fs/ceph/addr.c | 2 +-
fs/ceph/caps.c | 70 +++++++++++++++++++++++++++++++-------------
fs/ceph/inode.c | 61 ++++++++------------------------------
fs/ceph/snap.c | 10 +++++++
fs/ceph/super.h | 40 +++++++++++++++++++++----
include/linux/ceph/libceph.h | 7 ++---
net/ceph/ceph_common.c | 17 ++++-------
7 files changed, 115 insertions(+), 92 deletions(-)
next reply other threads:[~2021-02-22 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 14:21 Ilya Dryomov [this message]
2021-02-22 21:35 ` [GIT PULL] Ceph updates for 5.12-rc1 pr-tracker-bot
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=20210222142107.20046-1-idryomov@gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).