From: Anna Emese Nyiri <annaemesenyiri@gmail.com>
To: netdev@vger.kernel.org
Cc: fejes@inf.elte.hu, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemb@google.com, idosch@idosch.org,
horms@kernel.org, dsahern@kernel.org, linux-can@vger.kernel.org,
socketcan@hartkopp.net, mkl@pengutronix.de,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
tsbogend@alpha.franken.de, kaiyuanz@google.com,
James.Bottomley@HansenPartnership.com,
richard.henderson@linaro.org, arnd@arndb.de,
almasrymina@google.com, asml.silence@gmail.com,
linux-mips@vger.kernel.org, andreas@gaisler.com,
mattst88@gmail.com, kerneljasonxing@gmail.com,
sparclinux@vger.kernel.org, linux-alpha@vger.kernel.org,
linux-arch@vger.kernel.org, deller@gmx.de,
vadim.fedorenko@linux.dev, linux-parisc@vger.kernel.org,
Anna Emese Nyiri <annaemesenyiri@gmail.com>
Subject: [PATCH net-next v7 1/4] sock: Introduce sk_set_prio_allowed helper function
Date: Fri, 13 Dec 2024 09:44:54 +0100 [thread overview]
Message-ID: <20241213084457.45120-2-annaemesenyiri@gmail.com> (raw)
In-Reply-To: <20241213084457.45120-1-annaemesenyiri@gmail.com>
Simplify priority setting permissions with the 'sk_set_prio_allowed'
function, centralizing the validation logic. This change is made in
anticipation of a second caller in a following patch.
No functional changes.
Reviewed-by: Willem de Bruijn <willemb@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Suggested-by: Willem de Bruijn <willemb@google.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 74729d20cd00..9016f984d44e 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) {
@@ -1193,9 +1200,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-12-13 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 8:44 [PATCH net-next v7 0/4] Add support for SO_PRIORITY cmsg Anna Emese Nyiri
2024-12-13 8:44 ` Anna Emese Nyiri [this message]
2024-12-13 8:44 ` [PATCH net-next v7 2/4] sock: support " Anna Emese Nyiri
2024-12-13 8:44 ` [PATCH net-next v7 3/4] selftests: net: test SO_PRIORITY ancillary data with cmsg_sender Anna Emese Nyiri
2024-12-13 8:44 ` [PATCH net-next v7 4/4] sock: Introduce SO_RCVPRIORITY socket option Anna Emese Nyiri
2024-12-17 2:20 ` Jakub Kicinski
2024-12-18 11:57 ` Anna Nyiri
2024-12-17 2:30 ` [PATCH net-next v7 0/4] Add support for SO_PRIORITY cmsg patchwork-bot+netdevbpf
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=20241213084457.45120-2-annaemesenyiri@gmail.com \
--to=annaemesenyiri@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=almasrymina@google.com \
--cc=andreas@gaisler.com \
--cc=arnd@arndb.de \
--cc=asml.silence@gmail.com \
--cc=deller@gmx.de \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fejes@inf.elte.hu \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=kaiyuanz@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=shuah@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=sparclinux@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox