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>,
Francis Laniel <flaniel@linux.microsoft.com>
Subject: [RFC PATCH v2 2/2] kernel/ksysfs.c: Add capabilities attribute.
Date: Mon, 17 Jan 2022 15:12:54 +0100 [thread overview]
Message-ID: <20220117141254.46278-3-flaniel@linux.microsoft.com> (raw)
In-Reply-To: <20220117141254.46278-1-flaniel@linux.microsoft.com>
This new read-only attribute prints the capabilities values with their names:
0 CAP_CHOWN
1 CAP_DAC_OVERRIDE
...
39 CAP_BPF
Signed-off-by: Francis Laniel <flaniel@linux.microsoft.com>
---
kernel/ksysfs.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/kernel/ksysfs.c b/kernel/ksysfs.c
index 35859da8bd4f..7d39794a55bc 100644
--- a/kernel/ksysfs.c
+++ b/kernel/ksysfs.c
@@ -182,6 +182,23 @@ static ssize_t rcu_normal_store(struct kobject *kobj,
KERNEL_ATTR_RW(rcu_normal);
#endif /* #ifndef CONFIG_TINY_RCU */
+static ssize_t capabilities_show(struct kobject *unused0,
+ struct kobj_attribute *unused1, char *buf)
+{
+ int at = 0;
+ int i;
+
+ for (i = 0; i < CAP_LAST_CAP; i++) {
+ if (at >= PAGE_SIZE)
+ return at;
+
+ at += sysfs_emit_at(buf, at, "%d\t%s\n", i, cap_strings[i]);
+ }
+
+ return at;
+}
+KERNEL_ATTR_RO(capabilities);
+
/*
* Make /sys/kernel/notes give the raw contents of our kernel .notes section.
*/
@@ -229,6 +246,7 @@ static struct attribute * kernel_attrs[] = {
&rcu_expedited_attr.attr,
&rcu_normal_attr.attr,
#endif
+ &capabilities_attr.attr,
NULL
};
--
2.30.2
prev parent reply other threads:[~2022-01-17 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 14:12 [RFC PATCH v2 0/2] Add capabilities file to sysfs Francis Laniel
2022-01-17 14:12 ` [RFC PATCH v2 1/2] capability: Add cap_strings Francis Laniel
2022-01-17 14:12 ` Francis Laniel [this message]
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=20220117141254.46278-3-flaniel@linux.microsoft.com \
--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).