From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Anna Emese Nyiri <annaemesenyiri@gmail.com>, netdev@vger.kernel.org
Cc: fejes@inf.elte.hu, annaemesenyiri@gmail.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net-next v2 1/2] Introduce sk_set_prio_allowed helper function
Date: Sat, 02 Nov 2024 21:30:32 -0400 [thread overview]
Message-ID: <6726d23863738_2980c729459@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20241102125136.5030-2-annaemesenyiri@gmail.com>
Anna Emese Nyiri wrote:
> Simplifies the priority setting permissions through
> `sk_set_prio_allowed` function. No functional changes.
tiny, only because asking for changes in patch 2/2: please use
imperative mood: "Simplify". And maybe mention that this is in
anticipation of a second caller in a following patch.
> Suggested-by: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
> Signed-off-by: Anna Emese Nyiri <annaemesenyiri@gmail.com>
> ---
> net/core/sock.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/net/core/sock.c b/net/core/sock.c
> index 7f398bd07fb7..5ecf6f1a470c 100644
> --- a/net/core/sock.c
> +++ b/net/core/sock.c
> @@ -454,6 +454,13 @@ static int sock_set_timeout(long *timeo_p, sockptr_t optval, int optlen,
> return 0;
> }
>
> +static bool sk_set_prio_allowed(const struct sock *sk, int val)
> +{
> + return ((val >= TC_PRIO_BESTEFFORT && val <= TC_PRIO_INTERACTIVE) ||
> + sockopt_ns_capable(sock_net(sk)->user_ns, CAP_NET_RAW) ||
> + sockopt_ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN));
> +}
> +
> static bool sock_needs_netstamp(const struct sock *sk)
> {
> switch (sk->sk_family) {
> @@ -1187,9 +1194,7 @@ int sk_setsockopt(struct sock *sk, int level, int optname,
> /* handle options which do not require locking the socket. */
> switch (optname) {
> case SO_PRIORITY:
> - if ((val >= 0 && val <= 6) ||
> - sockopt_ns_capable(sock_net(sk)->user_ns, CAP_NET_RAW) ||
> - sockopt_ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN)) {
> + if (sk_set_prio_allowed(sk, val)) {
> sock_set_priority(sk, val);
> return 0;
> }
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-11-03 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 12:51 [PATCH net-next v2 0/2] support SO_PRIORITY cmsg Anna Emese Nyiri
2024-11-02 12:51 ` [PATCH net-next v2 1/2] Introduce sk_set_prio_allowed helper function Anna Emese Nyiri
2024-11-03 1:30 ` Willem de Bruijn [this message]
2024-11-02 12:51 ` [PATCH net-next v2 2/2] support SO_PRIORITY cmsg Anna Emese Nyiri
2024-11-03 1:27 ` Willem de Bruijn
2024-11-03 13:39 ` Anna Nyiri
2024-11-03 13:57 ` Willem de Bruijn
2024-11-03 15:41 ` [PATCH net-next v2 0/2] " Jakub Kicinski
2024-11-03 16:25 ` Ido Schimmel
2024-11-05 14:34 ` Anna Nyiri
2024-11-05 15:01 ` Willem de Bruijn
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=6726d23863738_2980c729459@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=annaemesenyiri@gmail.com \
--cc=edumazet@google.com \
--cc=fejes@inf.elte.hu \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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