summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorMaciej Żenczykowski <maze@google.com>2021-11-23 12:37:02 -0800
committerJakub Kicinski <kuba@kernel.org>2021-11-24 18:57:02 -0800
commita1b519b745489a54189e05ee934ada1b6bc595a3 (patch)
tree30522e188f9977b5b1137c77152256c07318379f /crypto
parent0898ca67b86e14207d4feb3f3fea8b87cec5aab1 (diff)
downloadlinux-a1b519b745489a54189e05ee934ada1b6bc595a3.tar.gz
linux-a1b519b745489a54189e05ee934ada1b6bc595a3.tar.bz2
linux-a1b519b745489a54189e05ee934ada1b6bc595a3.zip
net: allow CAP_NET_RAW to setsockopt SO_PRIORITY
CAP_NET_ADMIN is and should continue to be about configuring the system as a whole, not about configuring per-socket or per-packet parameters. Sending and receiving raw packets is what CAP_NET_RAW is all about. It can already send packets with any VLAN tag, and any IPv4 TOS mark, and any IPv6 TCLASS mark, simply by virtue of building such a raw packet. Not to mention using any protocol and source/ /destination ip address/port tuple. These are the fields that networking gear uses to prioritize packets. Hence, a CAP_NET_RAW process is already capable of affecting traffic prioritization after it hits the wire. This change makes it capable of affecting traffic prioritization even in the host at the nic and before that in the queueing disciplines (provided skb->priority is actually being used for prioritization, and not the TOS/TCLASS field) Hence it makes sense to allow a CAP_NET_RAW process to set the priority of sockets and thus packets it sends. Signed-off-by: Maciej Żenczykowski <maze@google.com> Link: https://lore.kernel.org/r/20211123203702.193221-1-zenczykowski@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions