From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Kumara Parameshwaran" <kumaraparamesh92@gmail.com>,
<jiayu.hu@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
"Kumara Parameshwaran" <kparameshwar@vmware.com>
Subject: RE: [PATCH v1] gro: bug fix in identifying 0 length tcp packets
Date: Mon, 4 Apr 2022 08:22:31 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D86F9C@smartserver.smartshare.dk> (raw)
In-Reply-To: <20220403115031.59632-1-kumaraparamesh92@gmail.com>
> From: Kumara Parameshwaran [mailto:kumaraparamesh92@gmail.com]
> Sent: Sunday, 3 April 2022 13.51
>
> As the minimum Ethernet frame size is 64 bytes, a 0 length
> tcp payload without tcp options would be 54 bytes and hence
> there would be padding. So it would be incorrect to use the
> packet length to determine the tcp data length.
>
> Fixes: 1e4cf4d6d4fb ("gro: cleanup")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kumara Parameshwaran <kparameshwar@vmware.com>
> ---
> v1:
> Do not use packet length to determine the tcp data length as
> the packet length could have padded bytes. This would lead
> to addition of 0 length tcp packets into the GRO layer when
> there ethernet fram is padded.
> lib/gro/gro_tcp4.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/lib/gro/gro_tcp4.c b/lib/gro/gro_tcp4.c
> index 7498c66..45e3f48 100644
> --- a/lib/gro/gro_tcp4.c
> +++ b/lib/gro/gro_tcp4.c
> @@ -198,7 +198,7 @@ gro_tcp4_reassemble(struct rte_mbuf *pkt,
> struct rte_tcp_hdr *tcp_hdr;
> uint32_t sent_seq;
> int32_t tcp_dl;
> - uint16_t ip_id, hdr_len, frag_off;
> + uint16_t ip_id, frag_off;
> uint8_t is_atomic;
>
> struct tcp4_flow_key key;
> @@ -217,7 +217,6 @@ gro_tcp4_reassemble(struct rte_mbuf *pkt,
> eth_hdr = rte_pktmbuf_mtod(pkt, struct rte_ether_hdr *);
> ipv4_hdr = (struct rte_ipv4_hdr *)((char *)eth_hdr + pkt-
> >l2_len);
> tcp_hdr = (struct rte_tcp_hdr *)((char *)ipv4_hdr + pkt->l3_len);
> - hdr_len = pkt->l2_len + pkt->l3_len + pkt->l4_len;
>
> /*
> * Don't process the packet which has FIN, SYN, RST, PSH, URG,
> ECE
> @@ -229,7 +228,7 @@ gro_tcp4_reassemble(struct rte_mbuf *pkt,
> * Don't process the packet whose payload length is less than or
> * equal to 0.
> */
> - tcp_dl = pkt->pkt_len - hdr_len;
> + tcp_dl = rte_be_to_cpu_16(ipv4_hdr->total_length) - (pkt->l3_len
> + pkt->l4_len);
> if (tcp_dl <= 0)
> return -1;
>
> --
> 2.7.4
>
Please confirm that this does not introduce a buffer overrun regarding malformed packets, e.g. a small packet with ipv4_hdr->total_length set to 65000.
I haven't looked at the patch in context, so my concern may be irrelevant.
-Morten
next prev parent reply other threads:[~2022-04-04 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 11:50 Kumara Parameshwaran
2022-04-04 6:22 ` Morten Brørup [this message]
2022-04-22 10:32 ` [PATCH v2] " Kumara Parameshwaran
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=98CBD80474FA8B44BF855DF32C47DC35D86F9C@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=kparameshwar@vmware.com \
--cc=kumaraparamesh92@gmail.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).