From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net, willemb@google.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net 0/2] udp6: allow SO_MARK ctrl msg to affect routing
Date: Fri, 29 Oct 2021 08:51:33 -0700 [thread overview]
Message-ID: <20211029155135.468098-1-kuba@kernel.org> (raw)
Hi!
Looks like SO_MARK from cmsg does not affect routing policy.
This seems accidental.
I opted for net because of the discrepancy between IPv4
and IPv6, but it never worked and doesn't cause crashes..
Jakub Kicinski (2):
udp6: allow SO_MARK ctrl msg to affect routing
selftests: udp: test for passing SO_MARK as cmsg
net/ipv6/udp.c | 2 +-
tools/testing/selftests/net/.gitignore | 1 +
tools/testing/selftests/net/Makefile | 2 +
tools/testing/selftests/net/cmsg_so_mark.c | 67 +++++++++++++++++++++
tools/testing/selftests/net/cmsg_so_mark.sh | 61 +++++++++++++++++++
5 files changed, 132 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/net/cmsg_so_mark.c
create mode 100755 tools/testing/selftests/net/cmsg_so_mark.sh
base-commit: 6de6e46d27ef386feecdbea56b3bfd6c3b3bc1f9
--
2.31.1
next reply other threads:[~2021-10-29 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 15:51 Jakub Kicinski [this message]
2021-10-29 15:51 ` [PATCH net 1/2] udp6: allow SO_MARK ctrl msg to affect routing Jakub Kicinski
2021-10-29 18:22 ` David Ahern
2021-10-30 1:23 ` Willem de Bruijn
2021-10-29 15:51 ` [PATCH net 2/2] selftests: udp: test for passing SO_MARK as cmsg Jakub Kicinski
2021-10-29 18:24 ` David Ahern
2021-10-30 1:14 ` Willem de Bruijn
2021-11-01 13:20 ` [PATCH net 0/2] udp6: allow SO_MARK ctrl msg to affect routing 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=20211029155135.468098-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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 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.