From: "Lena Wang (王娜)" <Lena.Wang@mediatek.com>
To: "jiri@resnulli.us" <jiri@resnulli.us>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dsahern@kernel.org" <dsahern@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"Shiming Cheng (成诗明)" <Shiming.Cheng@mediatek.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net v3] ipv6:flush ipv6 route cache when rule is changed
Date: Thu, 29 Feb 2024 08:47:39 +0000 [thread overview]
Message-ID: <263e5591e162a662b96a574b3629d0e82bd276f5.camel@mediatek.com> (raw)
In-Reply-To: <ZeBCpOAiQ_-DKEKi@nanopsycho>
On Thu, 2024-02-29 at 09:39 +0100, Jiri Pirko wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> Thu, Feb 29, 2024 at 09:24:54AM CET, Lena.Wang@mediatek.com wrote:
> >On Wed, 2024-02-28 at 16:50 +0100, Jiri Pirko wrote:
> >>
> >> External email : Please do not click links or open attachments
> until
> >> you have verified the sender or the content.
> >> Wed, Feb 28, 2024 at 04:38:56PM CET, Lena.Wang@mediatek.com
> wrote:
> >> >From: Shiming Cheng <shiming.cheng@mediatek.com>
> >> >
> >> >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.
> >> >
> >> >Signed-off-by: Shiming Cheng <shiming.cheng@mediatek.com>
> >> >Signed-off-by: Lena Wang <lena.wang@mediatek.com>
> >>
> >> 1) You are still missing Fixes tags, I don't know what to say.
> >I am sorry for the confuse. My previous change log of fix tag is a
> >wrong description for "PATCH net v2".
> >
> >Current patch doesn't fix previous commit. It is more like missing
> >flush since the first commit 101367c2f8c4 of creating fib6_rules.c.
> Is
> >it OK to add this fix or omit fix tag?
>
> No, the "Fixes" tag needs to be present. In this case, it looks like:
> Fixes: 101367c2f8c4 ("[IPV6]: Policy Routing Rules")
> Is the appropriate one. Isn't it?
>
OK, I will update it later in v4.
Many thanks.
> >
> >> 2) Re patch subject:
> >> "ipv6:flush ipv6 route cache when rule is changed"
> >> Could it be:
> >> "ipv6: fib6_rules: flush route cache when rule is changed"
> >> ? please.
> >Yes, I will update later in v4.
> >
> >> 3) Could you please honor the 24h hours resubmission rule:
> >>
> >
> https://www.kernel.org/doc/html/v6.6/process/maintainer-netdev.html#tl-dr
> >>
> >OK. I will follow the rule later.
> >
> >> pw-bot: cr
prev parent reply other threads:[~2024-02-29 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 15:38 Lena Wang (王娜)
2024-02-28 15:50 ` Jiri Pirko
2024-02-29 8:24 ` Lena Wang (王娜)
2024-02-29 8:39 ` Jiri Pirko
2024-02-29 8:47 ` Lena Wang (王娜) [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=263e5591e162a662b96a574b3629d0e82bd276f5.camel@mediatek.com \
--to=lena.wang@mediatek.com \
--cc=Shiming.Cheng@mediatek.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®