From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, ryan.e.hall@intel.com,
alexander.v.gutkin@intel.com,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] ip_frag: two fixes in reassembly code
Date: Mon, 5 Nov 2018 12:11:12 +0000 [thread overview]
Message-ID: <1541419874-31457-1-git-send-email-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <1541413603-4792-1-git-send-email-konstantin.ananyev@intel.com>
Fix 2 issues reported in reassembly code path.
Konstantin Ananyev (2):
ip_frag: check fragment length of incoming packet
ip_frag: use key length for key comparision
lib/librte_ip_frag/ip_frag_common.h | 14 ++++--------
lib/librte_ip_frag/rte_ip_frag.h | 14 +++++++++---
lib/librte_ip_frag/rte_ipv4_reassembly.c | 22 +++++++++++++------
lib/librte_ip_frag/rte_ipv6_reassembly.c | 28 +++++++++++++++++-------
4 files changed, 50 insertions(+), 28 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2018-11-05 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:26 [dpdk-dev] [PATCH " Konstantin Ananyev
2018-11-05 10:26 ` [dpdk-dev] [PATCH 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 11:37 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-11-05 10:26 ` [dpdk-dev] [PATCH 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-05 12:11 ` Konstantin Ananyev [this message]
2018-11-05 12:11 ` [dpdk-dev] [PATCH v2 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 12:11 ` [dpdk-dev] [PATCH 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-05 12:18 ` [dpdk-dev] [PATCH v2 0/2] ip_frag: two fixes in reassembly code Konstantin Ananyev
2018-11-06 0:58 ` Thomas Monjalon
2018-11-05 12:18 ` [dpdk-dev] [PATCH v2 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 12:18 ` [dpdk-dev] [PATCH v2 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-06 10:53 ` Burakov, Anatoly
2018-11-06 11:41 ` Ananyev, Konstantin
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=1541419874-31457-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--cc=alexander.v.gutkin@intel.com \
--cc=dev@dpdk.org \
--cc=ryan.e.hall@intel.com \
--cc=stable@dpdk.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).