From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-man@vger.kernel.org,
"Maciej Żenczykowski" <maze@google.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
"Matthias Gerstner" <matthias.gerstner@suse.com>,
"Avinesh Kumar" <akumar@suse.de>
Subject: Re: [PATCH 1/1] socket.7: Mention CAP_NET_RAW on SO_MARK
Date: Tue, 16 Jan 2024 16:14:06 +0100 [thread overview]
Message-ID: <ZaadPmLFCI4rsGy_@debian> (raw)
In-Reply-To: <20240116110418.2577798-1-pvorel@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi Petr,
On Tue, Jan 16, 2024 at 12:04:18PM +0100, Petr Vorel wrote:
> Added in 079925cce1d0 ("net: allow SO_MARK with CAP_NET_RAW") in v5.17.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Patch applied. Thanks!
Have a lovely day,
Alex
> ---
> man7/socket.7 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/man7/socket.7 b/man7/socket.7
> index 3ff8fe51b..3ebfc770b 100644
> --- a/man7/socket.7
> +++ b/man7/socket.7
> @@ -614,7 +614,9 @@ Changing the mark can be used for mark-based
> routing without netfilter or for packet filtering.
> Setting this option requires the
> .B CAP_NET_ADMIN
> -capability.
> +or
> +.B CAP_NET_RAW
> +(since Linux 5.17) capability.
> .TP
> .B SO_OOBINLINE
> If this option is enabled,
> --
> 2.43.0
>
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-16 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 11:04 [PATCH 1/1] socket.7: Mention CAP_NET_RAW on SO_MARK Petr Vorel
2024-01-16 15:14 ` Alejandro Colomar [this message]
2024-01-17 9:14 ` Petr Vorel
2024-01-17 12:02 ` Alejandro Colomar
2024-01-17 12:08 ` Petr Vorel
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=ZaadPmLFCI4rsGy_@debian \
--to=alx@kernel.org \
--cc=akumar@suse.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=matthias.gerstner@suse.com \
--cc=maze@google.com \
--cc=pvorel@suse.cz \
/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).