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 6.10-rc1
Date: Sat, 25 May 2024 11:57:37 +0200 [thread overview]
Message-ID: <20240525095738.3046298-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6:
Linux 6.9 (2024-05-12 14:12:29 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.10-rc1
for you to fetch changes up to 93a2221c9c1ae32643df67c482dc4c4c591b7514:
doc: ceph: update userspace command to get CephFS metadata (2024-05-23 10:35:47 +0200)
----------------------------------------------------------------
We have a series from Xiubo that adds support for additional access
checks based on MDS auth caps which were recently made available to
clients. This is needed to prevent scenarios where the MDS quietly
discards updates that a UID-restricted client previously (wrongfully)
acked to the user. Other than that, just a documentation fixup.
----------------------------------------------------------------
Artem Ikonnikov (1):
doc: ceph: update userspace command to get CephFS metadata
Xiubo Li (6):
ceph: save cap_auths in MDS client when session is opened
ceph: add ceph_mds_check_access() helper
ceph: check the cephx mds auth access for setattr
ceph: check the cephx mds auth access for open
ceph: check the cephx mds auth access for async dirop
ceph: add CEPHFS_FEATURE_MDS_AUTH_CAPS_CHECK feature bit
Documentation/filesystems/ceph.rst | 15 ++-
fs/ceph/dir.c | 28 ++++
fs/ceph/file.c | 66 ++++++++-
fs/ceph/inode.c | 46 +++++--
fs/ceph/mds_client.c | 270 ++++++++++++++++++++++++++++++++++++-
fs/ceph/mds_client.h | 28 +++-
6 files changed, 434 insertions(+), 19 deletions(-)
next reply other threads:[~2024-05-25 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 9:57 Ilya Dryomov [this message]
2024-05-25 21:32 ` 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=20240525095738.3046298-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
all inboxes | Powered by JetHome®