From: xiubli@redhat.com
To: idryomov@gmail.com, ceph-devel@vger.kernel.org
Cc: vshankar@redhat.com, mchangir@redhat.com, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v5 0/6] ceph: check the cephx mds auth access in client side
Date: Thu, 18 Apr 2024 22:20:13 +0800 [thread overview]
Message-ID: <20240418142019.133191-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
V5:
- fix incorrect git_t parsing, it should be int32_t.
Xiubo Li (6):
ceph: save the cap_auths in client when session being opened
ceph: add ceph_mds_check_access() helper support
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
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 ++++-
5 files changed, 425 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-18 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 14:20 xiubli [this message]
2024-04-18 14:20 ` [PATCH v5 1/6] ceph: save the cap_auths in client when session being opened xiubli
2024-04-18 14:20 ` [PATCH v5 2/6] ceph: add ceph_mds_check_access() helper support xiubli
2024-04-18 14:20 ` [PATCH v5 3/6] ceph: check the cephx mds auth access for setattr xiubli
2024-04-18 14:20 ` [PATCH v5 4/6] ceph: check the cephx mds auth access for open xiubli
2024-04-18 14:20 ` [PATCH v5 5/6] ceph: check the cephx mds auth access for async dirop xiubli
2024-04-18 14:20 ` [PATCH v5 6/6] ceph: add CEPHFS_FEATURE_MDS_AUTH_CAPS_CHECK feature bit xiubli
2024-05-23 3:31 ` [PATCH v5 0/6] ceph: check the cephx mds auth access in client side Milind Changire
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=20240418142019.133191-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=mchangir@redhat.com \
--cc=vshankar@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).