From: Sascha Grunert <saschagrunert@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Sascha Grunert <sgrunert@redhat.com>,
Sascha Grunert <saschagrunert@gmail.com>
Subject: [PATCH v2] proc.5: add Seccomp_filters entry
Date: Mon, 14 Aug 2023 10:33:21 +0200 [thread overview]
Message-ID: <20230814083321.503554-1-saschagrunert@gmail.com> (raw)
From: Sascha Grunert <sgrunert@redhat.com>
The field exists since Linux 5.9 (818c03) but have not been documented
yet.
Signed-off-by: Sascha Grunert <saschagrunert@gmail.com>
---
man5/proc.5 | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/man5/proc.5 b/man5/proc.5
index 04b45ccb7..c80b93e24 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -2551,6 +2551,7 @@ CapBnd: ffffffffffffffff
CapAmb: 0000000000000000
NoNewPrivs: 0
Seccomp: 0
+Seccomp_filters: 0
Speculation_Store_Bypass: vulnerable
Cpus_allowed: 00000001
Cpus_allowed_list: 0
@@ -2809,6 +2810,12 @@ This field is provided only if the kernel was built with the
.B CONFIG_SECCOMP
kernel configuration option enabled.
.TP
+.I Seccomp_filters
+.\" commit c818c03b661cd769e035e41673d5543ba2ebda64
+Number of seccomp filters attached to the process
+(since Linux 5.9, see
+.BR seccomp (2)).
+.TP
.I Speculation_Store_Bypass
.\" commit fae1fa0fc6cca8beee3ab8ed71d54f9a78fa3f64
Speculation flaw mitigation state
--
2.41.0
next reply other threads:[~2023-08-14 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 8:33 Sascha Grunert [this message]
2023-08-14 10:36 ` [PATCH v2] proc.5: add Seccomp_filters entry Alejandro Colomar
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=20230814083321.503554-1-saschagrunert@gmail.com \
--to=saschagrunert@gmail.com \
--cc=alx@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-man@vger.kernel.org \
--cc=sgrunert@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