route: update fnhe_expires for redirect when the fnhe exists
authorXin Long <lucien.xin@gmail.com>
Fri, 17 Nov 2017 06:27:06 +0000 (14:27 +0800)
committerSasha Levin <alexander.levin@microsoft.com>
Wed, 17 Jan 2018 17:55:27 +0000 (12:55 -0500)
commit3e3780098e9ffac153347f6bf6dabf0f3d20b135
tree082ce8291469ca1c53d2fffd5a4da69509049181
parent2f52207aba567a9e02e739e72c904ffd5edb042f
route: update fnhe_expires for redirect when the fnhe exists

[ Upstream commit e39d5246111399dbc6e11cd39fd8580191b86c47 ]

Now when creating fnhe for redirect, it sets fnhe_expires for this
new route cache. But when updating the exist one, it doesn't do it.
It will cause this fnhe never to be expired.

Paolo already noticed it before, in Jianlin's test case, it became
even worse:

When ip route flush cache, the old fnhe is not to be removed, but
only clean it's members. When redirect comes again, this fnhe will
be found and updated, but never be expired due to fnhe_expires not
being set.

So fix it by simply updating fnhe_expires even it's for redirect.

Fixes: aee06da6726d ("ipv4: use seqlock for nh_exceptions")
Reported-by: Jianlin Shi <jishi@redhat.com>
Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
net/ipv4/route.c