From: Petr Vorel <pvorel@suse.cz>
To: Alejandro Colomar <alx@kernel.org>
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: Wed, 17 Jan 2024 10:14:52 +0100 [thread overview]
Message-ID: <20240117091452.GB2665992@pevik> (raw)
In-Reply-To: <ZaadPmLFCI4rsGy_@debian>
Hi Alex,
> 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!
Thank you! BTW I don't see this patch in git tree [1], maybe you just haven't
push yet.
Kind regards,
Petr
[1] https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/
> 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
next prev parent reply other threads:[~2024-01-17 9:15 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
2024-01-17 9:14 ` Petr Vorel [this message]
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=20240117091452.GB2665992@pevik \
--to=pvorel@suse.cz \
--cc=akumar@suse.de \
--cc=alx@kernel.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.