From: Guillaume Nault <gnault@redhat.com>
To: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: [PATCH net 0/3] ipv6: Fix socket connection with DSCP fib-rules.
Date: Wed, 8 Feb 2023 18:13:56 +0100 [thread overview]
Message-ID: <cover.1675875519.git.gnault@redhat.com> (raw)
The "flowlabel" field of struct flowi6 is used to store both the actual
flow label and the DS Field (or Traffic Class). However the .connect
handlers of datagram and TCP sockets don't set the DS Field part when
doing their route lookup. This breaks fib-rules that match on DSCP.
Guillaume Nault (3):
ipv6: Fix datagram socket connect with DSCP.
ipv6: Fix tcp socket connect with DSCP.
selftests: fib_rule_tests: Test UDP and TCP connections with DSCP
rules.
net/ipv6/datagram.c | 2 +-
net/ipv6/tcp_ipv6.c | 1 +
tools/testing/selftests/net/fib_rule_tests.sh | 128 +++++++++++++++++-
tools/testing/selftests/net/nettest.c | 51 ++++++-
4 files changed, 179 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2023-02-08 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 17:13 Guillaume Nault [this message]
2023-02-08 17:13 ` [PATCH net 1/3] ipv6: Fix datagram socket connection with DSCP Guillaume Nault
2023-02-09 10:55 ` Eric Dumazet
2023-02-09 15:39 ` David Ahern
2023-02-08 17:14 ` [PATCH net 2/3] ipv6: Fix tcp " Guillaume Nault
2023-02-09 10:56 ` Eric Dumazet
2023-02-09 15:39 ` David Ahern
2023-02-08 17:14 ` [PATCH net 3/3] selftests: fib_rule_tests: Test UDP and TCP connections with DSCP rules Guillaume Nault
2023-02-09 15:42 ` David Ahern
2023-02-10 7:00 ` [PATCH net 0/3] ipv6: Fix socket connection with DSCP fib-rules 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=cover.1675875519.git.gnault@redhat.com \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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).