From: Xia Yan <yanxia@cmss.chinamobile.com>
To: willemdebruijn.kernel@gmail.com
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@kernel.org,
horms@kernel.org, idosch@nvidia.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, shuah@kernel.org,
stable@vger.kernel.org, tpluszz77@gmail.com, willemb@google.com,
yana06070@163.com
Subject: Re: [PATCH net v2 1/2] ipv6: fix cached route reuse for SO_MARK control messages
Date: Mon, 9 Nov 2026 09:58:45 +0800 [thread overview]
Message-ID: <20261109015838.14237-1-yanxia@cmss.chinamobile.com> (raw)
In-Reply-To: <willemdebruijn.kernel.1e0038bcc3ef8@gmail.com>
Hi Willem,
> Would this be a viable alternative solution?
Yes, I've used your approach in v3: the cache is read only when
connected is true.
All 54 cmsg_so_mark.sh cases pass on UML, including explicit mark 0.
v3:
https://lore.kernel.org/netdev/20261109014400.9025-1-yanxia@cmss.chinamobile.com/
Thanks,
Xia Yan
prev parent reply other threads:[~2026-11-09 1:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 9:22 Xia Yan
2026-11-04 9:22 ` [PATCH net v2 2/2] selftests: net: exercise SO_MARK on connected sockets Xia Yan
2026-11-04 9:23 ` Xia Yan
2026-11-05 9:39 ` netdev-bot+sashiko
2026-11-04 9:23 ` [PATCH net v2 1/2] ipv6: fix cached route reuse for SO_MARK control messages Xia Yan
2026-11-04 9:29 ` netdev-bot+sinfo
2026-11-04 9:50 ` Xia Yan
2026-11-05 9:38 ` netdev-bot+sashiko
2026-11-06 2:13 ` Xia Yan
2026-11-06 3:01 ` Willem de Bruijn
2026-11-06 3:14 ` Willem de Bruijn
2026-11-09 1:58 ` Xia Yan [this message]
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=20261109015838.14237-1-yanxia@cmss.chinamobile.com \
--to=yanxia@cmss.chinamobile.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tpluszz77@gmail.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yana06070@163.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
all inboxes | Powered by JetHome®