From: Ratheesh Kannoth <rkannoth@marvell.com>
To: James Lee <lizheng043@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"jmorris@namei.org" <jmorris@namei.org>,
"James.Z.Li@dell.com" <James.Z.Li@dell.com>
Subject: RE: [EXTERNAL] Re: [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full
Date: Mon, 18 Mar 2024 15:36:00 +0000 [thread overview]
Message-ID: <MWHPR1801MB19185089A3147123D1E877D0D32D2@MWHPR1801MB1918.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAPCnf4zS=FN0MHM2tQV0b468zN0yqRHbaNMsk3cDQ7Vu8wiHKA@mail.gmail.com>
> From: James Lee <lizheng043@gmail.com>
> Sent: Monday, March 18, 2024 2:09 PM
> To: Ratheesh Kannoth <rkannoth@marvell.com>
> Cc: linux-kernel@vger.kernel.org; netdev@vger.kernel.org;
> nhorman@tuxdriver.com; davem@davemloft.net; jmorris@namei.org;
> James.Z.Li@dell.com
> Subject: [EXTERNAL] Re: [PATCH] neighbour: guarantee the localhost
> connections be established successfully even the ARP table is full
>
> Prioritize security for external emails: Confirm sender and content safety
> before clicking links or opening attachments
>
> ----------------------------------------------------------------------
> loopback neigh is a special device in the neighbour system which is used by all
> local communications and state is NUD_NOARP.
> Any setting value of gc_thresh3 might encounter arp table be full, manually
> increasing gc_thresh3 can resolve this issue for every time, but we hope this
> issue automatically be resolved in Linux kernel for all local communications
> whenever ARP table is full, rather than manually operation as a workaround.
Issue is , these are dynamic entries which cannot be removed by gc. And there is no
Threshold applicable on it. I feel like, this may be exploited.
next prev parent reply other threads:[~2024-03-18 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:24 [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full Zheng Li
2024-03-11 13:51 ` Ratheesh Kannoth
2024-03-18 8:39 ` James Lee
2024-03-18 15:36 ` Ratheesh Kannoth [this message]
2024-03-19 9:42 ` [EXTERNAL] " James Lee
2024-03-22 3:37 ` Ratheesh Kannoth
2024-03-28 8:41 ` James Lee
2024-03-28 8:55 ` Ratheesh Kannoth
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=MWHPR1801MB19185089A3147123D1E877D0D32D2@MWHPR1801MB1918.namprd18.prod.outlook.com \
--to=rkannoth@marvell.com \
--cc=James.Z.Li@dell.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizheng043@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).