From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Cc: ranro@mellanox.com, tariqt@mellanox.com, Florian Westphal <fw@strlen.de>
Subject: [PATCH net-next 1/2] net: ipv4: fix infinite loop on secondary addr promotion
Date: Thu, 27 Jun 2019 14:03:32 +0200 [thread overview]
Message-ID: <20190627120333.12469-2-fw@strlen.de> (raw)
In-Reply-To: <20190627120333.12469-1-fw@strlen.de>
secondary address promotion causes infinite loop -- it arranges
for ifa->ifa_next to point back to itself.
Problem is that 'prev_prom' and 'last_prim' might point at the same entry,
so 'last_sec' pointer must be obtained after prev_prom->next update.
Fixes: 2638eb8b50cf ("net: ipv4: provide __rcu annotation for ifa_list")
Reported-by: Ran Rozenstein <ranro@mellanox.com>
Reported-by: Tariq Toukan <tariqt@mellanox.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
---
net/ipv4/devinet.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
index 7874303220c5..137d1892395d 100644
--- a/net/ipv4/devinet.c
+++ b/net/ipv4/devinet.c
@@ -428,8 +428,9 @@ static void __inet_del_ifa(struct in_device *in_dev,
if (prev_prom) {
struct in_ifaddr *last_sec;
- last_sec = rtnl_dereference(last_prim->ifa_next);
rcu_assign_pointer(prev_prom->ifa_next, next_sec);
+
+ last_sec = rtnl_dereference(last_prim->ifa_next);
rcu_assign_pointer(promote->ifa_next, last_sec);
rcu_assign_pointer(last_prim->ifa_next, promote);
}
--
2.21.0
next prev parent reply other threads:[~2019-06-27 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 12:03 [PATCH net-next 0/2] net: ipv4: fix circular-list infinite loop Florian Westphal
2019-06-27 12:03 ` Florian Westphal [this message]
2019-06-27 12:03 ` [PATCH net-next 2/2] selftests: rtnetlink: add small test case with 'promote_secondaries' enabled Florian Westphal
2019-06-27 16:54 ` [PATCH net-next 0/2] net: ipv4: fix circular-list infinite loop David Miller
2019-06-30 7:56 ` Tariq Toukan
2019-07-01 6:46 ` Ran Rozenstein
2019-07-01 7:21 ` Tariq Toukan
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=20190627120333.12469-2-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=ranro@mellanox.com \
--cc=tariqt@mellanox.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).