From: patchwork-bot+netdevbpf@kernel.org
To: Shiming Cheng <shiming.cheng@mediatek.com>
Cc: jiri@resnulli.us, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lena.wang@mediatek.com
Subject: Re: [PATCH net v5] ipv6: fib6_rules: flush route cache when rule is changed
Date: Fri, 08 Mar 2024 10:20:31 +0000 [thread overview]
Message-ID: <170989323111.6327.13031133027277965133.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240307100157.29699-1-shiming.cheng@mediatek.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Mar 2024 18:01:57 +0800 you wrote:
> When rule policy is changed, ipv6 socket cache is not refreshed.
> The sock's skb still uses a outdated route cache and was sent to
> a wrong interface.
>
> To avoid this error we should update fib node's version when
> rule is changed. Then skb's route will be reroute checked as
> route cache version is already different with fib node version.
> The route cache is refreshed to match the latest rule.
>
> [...]
Here is the summary with links:
- [net,v5] ipv6: fib6_rules: flush route cache when rule is changed
https://git.kernel.org/netdev/net/c/c4386ab4f6c6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-08 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 10:01 [PATCH net v5] ipv6: fib6_rules: flush route cache when rule is changed Shiming Cheng
2024-03-07 19:36 ` David Ahern
2024-03-08 10:20 ` patchwork-bot+netdevbpf [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=170989323111.6327.13031133027277965133.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lena.wang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shiming.cheng@mediatek.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;
as well as URLs for NNTP newsgroup(s).