From: "wanghai (M)" <wanghai38@huawei.com>
To: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <edumazet@google.com>,
<yoshfuji@linux-ipv6.org>, <dsahern@kernel.org>
Cc: <netdev@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] net: ipv4: The sent udp broadcast message may be converted to an arp request message
Date: Mon, 7 Feb 2022 22:09:49 +0800 [thread overview]
Message-ID: <55a04a8f-56f3-f73c-2aea-2195923f09d1@huawei.com> (raw)
Hello,
I found a bug, but I don't know how to fix it. Anyone have some good ideas?
This bug will cause udp broadcast messages not to be sent, but instead send
non-expected arp request messages.
Deleting the ip while sending udp broadcast messages and then configuring
the ip again will probably trigger the bug.
The following is the timing diagram of the bug, cpu0 sends a broadcast
message and cpu1 deletes the routing table at the appropriate time.
cpu0 cpu1
send()
udp_sendmsg()
ip_route_output_flow()
| fib_lookup()
udp_send_skb()
ip_send_skb()
ip_finish_output2()
ifconfig eth0:2 down
fib_del_ifaddr
fib_table_delete //
delete fib table
ip_neigh_for_gw()
| ip_neigh_gw4()
| __ipv4_neigh_lookup_noref()
| __neigh_create()
| tbl->constructor(n) --> arp_constructor()
| neigh->type = inet_addr_type_dev_table(); // no
route, neigh->type = RTN_UNICAST
neigh_output() // unicast, send an arp request and create an
exception arp entry
After the above operation, an abnormal arp entry will be generated. If
the ip is configured again(ifconfig eth0:2 12.0.208.0), the abnormal arp
entry will still exist, and the udp broadcast message will be converted
to an arp request message when it is sent.
Any feedback would be appreciated, thanks.
--
Wang Hai
next reply other threads:[~2022-02-07 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 14:09 wanghai (M) [this message]
2022-02-08 7:51 ` [BUG] net: ipv4: The sent udp broadcast message may be converted to an arp request message Ido Schimmel
2022-02-08 9:18 ` wanghai (M)
2022-02-16 3:19 ` wanghai (M)
2022-02-16 7:29 ` Ido Schimmel
2022-02-16 8:03 ` wanghai (M)
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=55a04a8f-56f3-f73c-2aea-2195923f09d1@huawei.com \
--to=wanghai38@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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