From: Paolo Abeni <pabeni@redhat.com>
To: "Li, James Zheng" <James.Z.Li@Dell.com>,
Eric Dumazet <edumazet@google.com>,
Zheng Li <lizheng043@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"jmorris@namei.org" <jmorris@namei.org>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full
Date: Thu, 18 Apr 2024 11:33:46 +0200 [thread overview]
Message-ID: <3f487ef495da476e5b0564dbb024dca54e8bee10.camel@redhat.com> (raw)
In-Reply-To: <IA1PR19MB6545F5F1940C0B326058987ABB082@IA1PR19MB6545.namprd19.prod.outlook.com>
On Tue, 2024-04-16 at 10:36 +0000, Li, James Zheng wrote:
> On Tuesday, April 16, 2024 6:02 PM Eric Dumazet <edumazet@google.com> wrote:
> > Hmmm...
>
> > Loopback IPv4 can hold 2^24 different addresses, that is 16384 * 1024
>
> There is only one Loopback neigh "0.0.0.0 dev lo lladdr 00:00:00:00:00:00 NOARP"
> existing even you have configured 2^24 different addresses on the loopback device.
Eric, I think James is right, in __ipv4_neigh_lookup_noref():
if (dev->flags & (IFF_LOOPBACK | IFF_POINTOPOINT))
key = INADDR_ANY;
return ___neigh_lookup_noref(&arp_tbl, neigh_key_eq32, arp_hashfn, &key, dev);
So there should be at most one neigh entry over the loopback device.
The patch looks safe to me, am I missing something?
Thanks,
Paolo
next prev parent reply other threads:[~2024-04-18 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:53 [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full Zheng Li
2024-04-16 10:02 ` Eric Dumazet
2024-04-16 10:36 ` Li, James Zheng
2024-04-18 9:33 ` Paolo Abeni [this message]
2024-04-18 9:45 ` Eric Dumazet
2024-04-18 10:20 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 12:25 Zheng Li
2024-04-15 18:07 ` Jakub Kicinski
2024-04-15 18:15 ` Simon Horman
2024-03-11 12:24 Zheng Li
2024-03-11 13:51 ` Ratheesh Kannoth
2024-03-18 8:39 ` James Lee
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=3f487ef495da476e5b0564dbb024dca54e8bee10.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=James.Z.Li@Dell.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kuba@kernel.org \
--cc=lizheng043@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).