From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, willemb@google.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org, Xintong Hu <huxintong@fb.com>
Subject: Re: [PATCH net 1/2] udp6: allow SO_MARK ctrl msg to affect routing
Date: Fri, 29 Oct 2021 12:22:49 -0600 [thread overview]
Message-ID: <ff189fbe-7b72-44ec-266e-1613930fb8cf@gmail.com> (raw)
In-Reply-To: <20211029155135.468098-2-kuba@kernel.org>
On 10/29/21 9:51 AM, Jakub Kicinski wrote:
> Commit c6af0c227a22 ("ip: support SO_MARK cmsg")
> added propagation of SO_MARK from cmsg to skb->mark.
> For IPv4 and raw sockets the mark also affects route
> lookup, but in case of IPv6 the flow info is
> initialized before cmsg is parsed.
>
> Fixes: c6af0c227a22 ("ip: support SO_MARK cmsg")
> Reported-and-tested-by: Xintong Hu <huxintong@fb.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> net/ipv6/udp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2021-10-29 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 15:51 [PATCH net 0/2] udp6: allow SO_MARK ctrl msg to affect routing Jakub Kicinski
2021-10-29 15:51 ` [PATCH net 1/2] " Jakub Kicinski
2021-10-29 18:22 ` David Ahern [this message]
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=ff189fbe-7b72-44ec-266e-1613930fb8cf@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=huxintong@fb.com \
--cc=kuba@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 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).