From: Jeff Layton <jlayton@kernel.org>
To: Luis Henriques <lhenriques@suse.de>, Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ceph: add ceph.caps vxattr
Date: Mon, 23 Nov 2020 11:43:03 -0500 [thread overview]
Message-ID: <a12a732b67245cc02344405f7dd9fef4f3b47fbc.camel@kernel.org> (raw)
In-Reply-To: <20201123145311.13588-1-lhenriques@suse.de>
On Mon, 2020-11-23 at 14:53 +0000, Luis Henriques wrote:
> Add a new vxattr that allows userspace to list the caps for a specific
> directory or file.
>
> Signed-off-by: Luis Henriques <lhenriques@suse.de>
> ---
> fs/ceph/xattr.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/fs/ceph/xattr.c b/fs/ceph/xattr.c
> index 197cb1234341..996512e05513 100644
> --- a/fs/ceph/xattr.c
> +++ b/fs/ceph/xattr.c
> @@ -303,6 +303,18 @@ static ssize_t ceph_vxattrcb_snap_btime(struct ceph_inode_info *ci, char *val,
> ci->i_snap_btime.tv_nsec);
> }
>
>
>
>
> +static ssize_t ceph_vxattrcb_caps(struct ceph_inode_info *ci, char *val,
> + size_t size)
> +{
> + int issued;
> +
> + spin_lock(&ci->i_ceph_lock);
> + issued = __ceph_caps_issued(ci, NULL);
> + spin_unlock(&ci->i_ceph_lock);
> +
> + return ceph_fmt_xattr(val, size, "%s", ceph_cap_string(issued));
> +}
I wonder if we ought to print a numerical (hex) representation of the
cap set here in addition to the ceph_cap_string. A main use-case for
this will be in testcases, and determining whether (e.g.) Fs is in the
mask may be easier to do with a bitwise AND rather than having to parse
a string of text.
> +
> #define CEPH_XATTR_NAME(_type, _name) XATTR_CEPH_PREFIX #_type "." #_name
> #define CEPH_XATTR_NAME2(_type, _name, _name2) \
> XATTR_CEPH_PREFIX #_type "." #_name "." #_name2
> @@ -378,6 +390,13 @@ static struct ceph_vxattr ceph_dir_vxattrs[] = {
> .exists_cb = ceph_vxattrcb_snap_btime_exists,
> .flags = VXATTR_FLAG_READONLY,
> },
> + {
> + .name = "ceph.caps",
> + .name_size = sizeof("ceph.caps"),
> + .getxattr_cb = ceph_vxattrcb_caps,
> + .exists_cb = NULL,
> + .flags = VXATTR_FLAG_HIDDEN,
> + },
> { .name = NULL, 0 } /* Required table terminator */
> };
>
>
>
>
> @@ -403,6 +422,13 @@ static struct ceph_vxattr ceph_file_vxattrs[] = {
> .exists_cb = ceph_vxattrcb_snap_btime_exists,
> .flags = VXATTR_FLAG_READONLY,
> },
> + {
> + .name = "ceph.caps",
> + .name_size = sizeof("ceph.caps"),
> + .getxattr_cb = ceph_vxattrcb_caps,
> + .exists_cb = NULL,
> + .flags = VXATTR_FLAG_HIDDEN,
> + },
> { .name = NULL, 0 } /* Required table terminator */
> };
>
>
>
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-11-23 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:53 [RFC PATCH] ceph: add ceph.caps vxattr Luis Henriques
2020-11-23 15:17 ` Jeff Layton
2020-11-23 16:43 ` Jeff Layton [this message]
2020-11-23 17:38 ` [PATCH v2] " Luis Henriques
2020-11-24 13:09 ` Jeff Layton
2020-11-24 13:15 ` Luis Henriques
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=a12a732b67245cc02344405f7dd9fef4f3b47fbc.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.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).