[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220208183157.922752-1-jmaloy@redhat.com>
Date: Tue, 8 Feb 2022 13:31:57 -0500
From: jmaloy@...hat.com
To: netdev@...r.kernel.org, davem@...emloft.net
Cc: kuba@...nel.org, tipc-discussion@...ts.sourceforge.net,
tung.q.nguyen@...tech.com.au, hoang.h.le@...tech.com.au,
tuong.t.lien@...tech.com.au, jmaloy@...hat.com, maloy@...jonn.com,
xinl@...hat.com, ying.xue@...driver.com,
parthasarathy.bhuvaragan@...il.com
Subject: [net-next] tipc: rate limit warning for received illegal binding update
From: Jon Maloy <jmaloy@...hat.com>
It would be easy to craft a message containing an illegal binding table
update operation. This is handled correctly by the code, but the
corresponding warning printout is not rate limited as is should be.
We fix this now.
Signed-off-by: Jon Maloy <jmaloy@...hat.com>
---
net/tipc/name_distr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/tipc/name_distr.c b/net/tipc/name_distr.c
index bda902caa814..8267b751a526 100644
--- a/net/tipc/name_distr.c
+++ b/net/tipc/name_distr.c
@@ -313,7 +313,7 @@ static bool tipc_update_nametbl(struct net *net, struct distr_item *i,
pr_warn_ratelimited("Failed to remove binding %u,%u from %u\n",
ua.sr.type, ua.sr.lower, node);
} else {
- pr_warn("Unrecognized name table message received\n");
+ pr_warn_ratelimited("Unknown name table message received\n");
}
return false;
}
--
2.31.1
Powered by blists - more mailing lists