From: Chinmay Agarwal <chinagar@codeaurora.org>
To: netdev@vger.kernel.org
Cc: xiyou.wangcong@gmail.com, sharathv@codeaurora.org
Subject: [PATCH] neighbour: Prevent a dead entry from updating gc_list
Date: Tue, 26 Jan 2021 01:29:37 +0530 [thread overview]
Message-ID: <20210125195927.GA26972@chinagar-linux.qualcomm.com> (raw)
Following race condition was detected:
<CPU A, t0> - neigh_flush_dev() is under execution and calls neigh_mark_dead(n),
marking the neighbour entry 'n' as dead.
<CPU B, t1> - Executing: __netif_receive_skb() -> __netif_receive_skb_core()
-> arp_rcv() -> arp_process().arp_process() calls __neigh_lookup() which takes
a reference on neighbour entry 'n'.
<CPU A, t2> - Moves further along neigh_flush_dev() and calls
neigh_cleanup_and_release(n), but since reference count increased in t2,
'n' couldn't be destroyed.
<CPU B, t3> - Moves further along, arp_process() and calls
neigh_update()-> __neigh_update() -> neigh_update_gc_list(), which adds
the neighbour entry back in gc_list(neigh_mark_dead(), removed it
earlier in t0 from gc_list)
<CPU B, t4> - arp_process() finally calls neigh_release(n), destroying
the neighbour entry.
This leads to 'n' still being part of gc_list, but the actual
neighbour structure has been freed.
The situation can be prevented from happening if we disallow a dead
entry to have any possibility of updating gc_list. This is what the
patch intends to achieve.
Signed-off-by: Chinmay Agarwal <chinagar@codeaurora.org>
---
net/core/neighbour.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index ff07358..cf8e3076 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -1244,13 +1244,14 @@ static int __neigh_update(struct neighbour *neigh, const u8 *lladdr,
old = neigh->nud_state;
err = -EPERM;
- if (!(flags & NEIGH_UPDATE_F_ADMIN) &&
- (old & (NUD_NOARP | NUD_PERMANENT)))
- goto out;
if (neigh->dead) {
NL_SET_ERR_MSG(extack, "Neighbor entry is now dead");
+ new=old;
goto out;
}
+ if (!(flags & NEIGH_UPDATE_F_ADMIN) &&
+ (old & (NUD_NOARP | NUD_PERMANENT)))
+ goto out;
ext_learn_change = neigh_update_ext_learned(neigh, flags, ¬ify);
--
next reply other threads:[~2021-01-25 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 19:59 Chinmay Agarwal [this message]
2021-01-25 21:07 ` [PATCH] neighbour: Prevent a dead entry from updating gc_list Cong Wang
2021-01-25 21:59 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2021-01-27 16:54 Chinmay Agarwal
2021-01-28 2:34 ` Cong Wang
2021-01-30 16:05 ` David Ahern
2021-02-02 1:09 ` Jakub Kicinski
2021-01-25 19:49 Chinmay Agarwal
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=20210125195927.GA26972@chinagar-linux.qualcomm.com \
--to=chinagar@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=sharathv@codeaurora.org \
--cc=xiyou.wangcong@gmail.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).