From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>,
Sascha Grunert <saschagrunert@gmail.com>
Cc: lnx-man <linux-man@vger.kernel.org>, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] proc.5: add Seccomp_filters entry
Date: Sat, 12 Aug 2023 20:09:02 +0200 [thread overview]
Message-ID: <98679f80-dd4c-c8a5-14ca-c4fa7f1f4bb3@kernel.org> (raw)
In-Reply-To: <CACKs7VATxovBTn3Ez5Ys-MUo0cKSO8YnfDRSFv5gj2c0SuXsbA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1569 bytes --]
On 2023-08-11 15:53, Stefan Puiu wrote:
> Hi Sasha,
>
> Small nit below.
>
>
> vin., 11 aug. 2023, 11:44 Sascha Grunert <saschagrunert@gmail.com> a scris:
>
>> 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 attached seccomp filters to the process
>> +(since Linux 5.9, see
>> +.BR seccomp (2)).
>> +.TP
>>
>
> I think "number of seccomp filters attached to..." sounds better, though
> I'm not a native English speaker.
+1
>
> Stefan.
>
> .I Speculation_Store_Bypass
>> .\" commit fae1fa0fc6cca8beee3ab8ed71d54f9a78fa3f64
>> Speculation flaw mitigation state
>> --
>> 2.41.0
>>
>>
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-12 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:26 [PATCH] proc.5: add Seccomp_filters entry Sascha Grunert
[not found] ` <CACKs7VATxovBTn3Ez5Ys-MUo0cKSO8YnfDRSFv5gj2c0SuXsbA@mail.gmail.com>
2023-08-12 18:09 ` Alejandro Colomar [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=98679f80-dd4c-c8a5-14ca-c4fa7f1f4bb3@kernel.org \
--to=alx@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-man@vger.kernel.org \
--cc=saschagrunert@gmail.com \
--cc=stefan.puiu@gmail.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