From: Francis Laniel <flaniel@linux.microsoft.com>
To: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org,
Serge Hallyn <serge@hallyn.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [RFC PATCH v3 2/2] security/inode.c: Add capabilities file.
Date: Fri, 21 Jan 2022 09:58:34 +0100 [thread overview]
Message-ID: <7787651.jkfHb4QSSr@machine> (raw)
In-Reply-To: <20220120180116.167702-3-flaniel@linux.microsoft.com>
Hi.
Le jeudi 20 janvier 2022, 19:01:16 CET Francis Laniel a écrit :
> This new read-only file prints the capabilities values with their names:
> cat /sys/kernel/security/capabilities
> 0 CAP_CHOWN
> 1 CAP_DAC_OVERRIDE
> ...
> 40 CAP_CHECKPOINT_RESTORE
>
> Signed-off-by: Francis Laniel <flaniel@linux.microsoft.com>
> ---
> security/inode.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/security/inode.c b/security/inode.c
> index 6c326939750d..cef78b497bab 100644
> --- a/security/inode.c
> +++ b/security/inode.c
> @@ -21,6 +21,7 @@
> #include <linux/security.h>
> #include <linux/lsm_hooks.h>
> #include <linux/magic.h>
> +#include <linux/capability.h>
>
> static struct vfsmount *mount;
> static int mount_count;
> @@ -328,6 +329,19 @@ static const struct file_operations lsm_ops = {
> };
> #endif
>
> +static struct dentry *capabilities_dentry;
> +static ssize_t capabilities_read(struct file *unused, char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> + return simple_read_from_buffer(buf, count, ppos, cap_string,
> + strlen(cap_string));
> +}
> +
> +static const struct file_operations capabilities_ops = {
> + .read = capabilities_read,
> + .llseek = generic_file_llseek,
> +};
> +
> static int __init securityfs_init(void)
> {
> int retval;
> @@ -345,6 +359,8 @@ static int __init securityfs_init(void)
> lsm_dentry = securityfs_create_file("lsm", 0444, NULL, NULL,
> &lsm_ops);
> #endif
> + capabilities_dentry = securityfs("capabilities", 0444, NULL, NULL,
> + capabilities_ops);
Sorry, I sent the old version of the patch and did not fixup this...
Kernel robot kindly show me this error.
I swear the output in the cover letter was done on the compiled kernel within
a VM.
I will send a v4 correcting this but I will wait to get some reviews on v3 to
not send to not generate too much traffic here.
> return 0;
> }
> core_initcall(securityfs_init);
Best regards.
next prev parent reply other threads:[~2022-01-21 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:01 [RFC PATCH v3 0/2] Add capabilities file to sysfs Francis Laniel
2022-01-20 18:01 ` [RFC PATCH v3 1/2] capability: Add cap_string Francis Laniel
2022-01-20 18:01 ` [RFC PATCH v3 2/2] security/inode.c: Add capabilities file Francis Laniel
2022-01-21 8:58 ` Francis Laniel [this message]
2022-01-20 18:09 ` [RFC PATCH v3 0/2] Add capabilities file to sysfs Casey Schaufler
2022-01-20 18:14 ` Francis Laniel
2022-01-20 18:20 ` Eric W. Biederman
2022-01-20 19:01 ` Francis Laniel
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=7787651.jkfHb4QSSr@machine \
--to=flaniel@linux.microsoft.com \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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 NNTP newsgroup(s).