mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lena Wang (王娜)" <Lena.Wang@mediatek.com>
To: "davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"dsahern@kernel.org" <dsahern@kernel.org>,
	"edumazet@google.com" <edumazet@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Shiming Cheng (成诗明)" <Shiming.Cheng@mediatek.com>
Subject: [PATCH] Net:cache didn't flush when ipv6 rule changed
Date: Mon, 26 Feb 2024 13:11:01 +0000	[thread overview]
Message-ID: <3efcbaf0872481d1a842eb9e18fa368b4b94d940.camel@mediatek.com> (raw)

From a415abaf4fc90a27dd86357ea8be62d32956f7d8 Mon Sep 17 00:00:00 2001
From: shiming cheng <shiming.cheng@mediatek.com>
Date: Mon, 26 Feb 2024 20:17:58 +0800
Subject: [PATCH] Net:cache didn't flush when ipv6 rule changed

When changed from old rule&route configure to new one as below,
ipv6 cache dst_entry did not change to new route table as no
cache flush callback function, then forward to wrong out interface.
When fib6_check dst_entry, the fib6_node version[fn_sernm] is
always the same with socket dst_cookie, old cache dst_entry is
always used and no chance to update.

So we need to update fib6_node version when rule changed and
flush cache to avoid dispatching a wrong interface.

Signed-off-by: shiming cheng <shiming.cheng@mediatek.com>
---
 net/ipv6/fib6_rules.c | 10 ++++++++++
 1 files changed, 10 insertions(+)

diff --git a/net/ipv6/fib6_rules.c b/net/ipv6/fib6_rules.c
index 7523c4baef35..bec2cf4436e1 100644
--- a/net/ipv6/fib6_rules.c
+++ b/net/ipv6/fib6_rules.c
@@ -449,6 +449,15 @@ static size_t fib6_rule_nlmsg_payload(struct
fib_rule *rule)
               + nla_total_size(16); /* src */
 }

+static void fib6_rule_flush_cache(struct fib_rules_ops *ops)
+{
+       struct net *net = ops->fro_net;
+       if (!net)
+               return;
+       rt_genid_bump_ipv6(net);
+       return;
+}
+
 static const struct fib_rules_ops __net_initconst
fib6_rules_ops_template = {
        .family                 = AF_INET6,
        .rule_size              = sizeof(struct fib6_rule),
@@ -461,6 +470,7 @@ static const struct fib_rules_ops __net_initconst
fib6_rules_ops_template = {
        .compare                = fib6_rule_compare,
        .fill                   = fib6_rule_fill,
        .nlmsg_payload          = fib6_rule_nlmsg_payload,
+       .flush_cache    = fib6_rule_flush_cache,
        .nlgroup                = RTNLGRP_IPV6_RULE,
        .owner                  = THIS_MODULE,
        .fro_net                = &init_net,
--
2.18.0

             reply	other threads:[~2024-02-26 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 13:11 Lena Wang (王娜) [this message]
2024-02-27 15:06 ` David Ahern
2024-02-28  7:28   ` Lena Wang (王娜)
2024-02-28  7:34     ` Paolo Abeni
2024-02-28  8:24 ` [PATCH net v2] " Lena Wang (王娜)
2024-02-28 12:30   ` Jiri Pirko

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=3efcbaf0872481d1a842eb9e18fa368b4b94d940.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=kuba@kernel.org \
    --cc=linux-kernel@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®