DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: Ben Magistro <koncept1@gmail.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"ben.magistro@trinitycyber.com" <ben.magistro@trinitycyber.com>,
	Stefan Baranoff <stefan.baranoff@trinitycyber.com>
Subject: Re: [dpdk-dev] Overriding rte_config.h
Date: Thu, 4 Nov 2021 07:51:24 -0700	[thread overview]
Message-ID: <20211104075124.4d09a23a@hermes.local> (raw)
In-Reply-To: <DM6PR11MB44913B2EEF25ADE0429D9BA59A8D9@DM6PR11MB4491.namprd11.prod.outlook.com>

On Thu, 4 Nov 2021 11:03:21 +0000
"Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:

> Hi Ben,
> 
> I also don’t think 64 is a common case here.
> For such cases we probably should think up some different approach for the reassembly table.

Larger values make it easier to DoS the IP fragment table.
See the Linux fragsmack vulnerability.

      reply	other threads:[~2021-11-04 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 13:48 Ben Magistro
2021-11-01 15:03 ` Bruce Richardson
2021-11-02 11:20   ` Ananyev, Konstantin
2021-11-02 12:07     ` Bruce Richardson
2021-11-02 12:24       ` Ananyev, Konstantin
2021-11-02 14:19         ` Bruce Richardson
2021-11-02 15:00           ` Ananyev, Konstantin
2021-11-03 14:38             ` Ben Magistro
2021-11-04 11:03               ` Ananyev, Konstantin
2021-11-04 14:51                 ` Stephen Hemminger [this message]

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=20211104075124.4d09a23a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=ben.magistro@trinitycyber.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=koncept1@gmail.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=stefan.baranoff@trinitycyber.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).