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 fixes for 6.5-rc1
Date: Fri, 7 Jul 2023 18:16:58 +0200 [thread overview]
Message-ID: <20230707161658.372600-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 6995e2de6891c724bfeb2db33d7b87775f913ad1:
Linux 6.4 (2023-06-25 16:29:58 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.5-rc1
for you to fetch changes up to 257e6172ab36ebbe295a6c9ee9a9dd0fe54c1dc2:
ceph: don't let check_caps skip sending responses for revoke msgs (2023-06-30 12:08:55 +0200)
----------------------------------------------------------------
A bunch of CephFS fixups from Xiubo, mostly around dropping caps, along
with a fix for a regression in the readahead handling code which sneaked
in with the switch to netfs helpers.
----------------------------------------------------------------
Xiubo Li (8):
ceph: only send metrics when the MDS rank is ready
ceph: try to dump the msgs when decoding fails
ceph: voluntarily drop Xx caps for requests those touch parent mtime
ceph: add a dedicated private data for netfs rreq
ceph: fix blindly expanding the readahead windows
ceph: trigger to flush the buffer when making snapshot
ceph: issue a cap release immediately if no cap exists
ceph: don't let check_caps skip sending responses for revoke msgs
fs/ceph/addr.c | 85 +++++++++++++++++++++++++++++++++++++++++-----------
fs/ceph/caps.c | 55 +++++++++++++++++++++++++++-------
fs/ceph/dir.c | 17 ++++++-----
fs/ceph/file.c | 3 +-
fs/ceph/mds_client.c | 4 +++
fs/ceph/metric.c | 8 +++++
fs/ceph/snap.c | 9 ++++--
fs/ceph/super.h | 13 ++++++++
8 files changed, 154 insertions(+), 40 deletions(-)
next reply other threads:[~2023-07-07 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 16:16 Ilya Dryomov [this message]
2023-07-07 22:26 ` [GIT PULL] Ceph fixes for 6.5-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=20230707161658.372600-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.