DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "guohongzhi (A)" <guohongzhi1@huawei.com>, <dev@dpdk.org>
Cc: <olivier.matz@6wind.com>, <konstantin.ananyev@intel.com>,
	<jiayu.hu@intel.com>, <ferruh.yigit@intel.com>,
	<nicolas.chautru@intel.com>, <cristian.dumitrescu@intel.com>,
	"Zhoujingbin (Robin, Russell Lab)" <zhoujingbin@huawei.com>,
	"chenchanghu" <chenchanghu@huawei.com>,
	"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
	"Linhaifeng" <haifeng.lin@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] lib/librte_net: fix bug for ipv4 checksumcalculating
Date: Fri, 15 May 2020 12:03:47 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C60FCB@smartserver.smartshare.dk> (raw)
In-Reply-To: <a03f56cd2e4a41abb68e927d91f281bd@huawei.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of guohongzhi (A)
> Sent: Friday, May 15, 2020 3:05 AM
> 
> Ok, later I will write a patch to solve the problem of tcpdump checksum
> 
> -----Original Message-----
> From: Morten Brørup [mailto:mb@smartsharesystems.com]
> Sent: Thursday,May 14,2020 20:57
> To: guohongzhi (A) <guohongzhi1@huawei.com>; dev@dpdk.org
> Cc: olivier.matz@6wind.com; konstantin.ananyev@intel.com;
> jiayu.hu@intel.com; ferruh.yigit@intel.com; nicolas.chautru@intel.com;
> cristian.dumitrescu@intel.com; Zhoujingbin (Robin, Russell Lab)
> <zhoujingbin@huawei.com>; chenchanghu <chenchanghu@huawei.com>; Lilijun
> (Jerry) <jerry.lilijun@huawei.com>; Linhaifeng <haifeng.lin@huawei.com>
> Subject: RE: [dpdk-dev] [PATCH] lib/librte_net: fix bug for ipv4
> checksumcalculating
> 
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of guohongzhi
> > Sent: Thursday, May 14, 2020 3:27 AM
> >
> > The function of rte_ipv4_cksum for calculating the checksum of IPv4
> > header is incorrect.
> > This function will return checksum value like 0xffff.
> > This value, however, is considered an illegal checksum on some
> > switches(like Trident3).
> >
> > RFC 1624 specifies the IPv4 checksum as follows:
> > https://tools.ietf.org/rfc/rfc1624
> > Since there is guaranteed to be at least one
> >    non-zero field in the IP header, and the checksum field in the
> >    protocol header is the complement of the sum, the checksum field
> can
> >    never contain ~(+0), which is -0 (0xFFFF).  It can, however,
> contain
> >    ~(-0), which is +0 (0x0000).
> >
> > ---
> >  lib/librte_net/rte_ip.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/librte_net/rte_ip.h b/lib/librte_net/rte_ip.h index
> > 1ceb7b7..ece2e43 100644
> > --- a/lib/librte_net/rte_ip.h
> > +++ b/lib/librte_net/rte_ip.h
> > @@ -267,7 +267,7 @@ rte_ipv4_cksum(const struct rte_ipv4_hdr
> > *ipv4_hdr)  {
> >  	uint16_t cksum;
> >  	cksum = rte_raw_cksum(ipv4_hdr, sizeof(struct rte_ipv4_hdr));
> > -	return (cksum == 0xffff) ? cksum : (uint16_t)~cksum;
> > +	return (uint16_t)~cksum;
> >  }
> >
> >  /**
> > --
> > 2.21.0.windows.1
> >
> >
> 
> Well spotted!
> 
> Reviewed-By: Morten Brørup <mb@smartsharesystems.com>
> 

While you are at it, you could also fix a Big Endian bug in __rte_raw_cksum():

	/* if length is in odd bytes */
	if (len == 1)
+#if RTE_BYTE_ORDER == RTE_BIG_ENDIAN
+		sum += *((const uint8_t *)u16_buf) << 8;
+#else
		sum += *((const uint8_t *)u16_buf);
+#endif

	return sum;

> 
> Would you consider writing another patch splitting
> rte_ipv4_udptcp_cksum() up into rte_ipv4_udp_cksum() and
> rte_ipv4_tcp_cksum(), so the TCP checksum will be calculated correctly?
> 
> RFC 768 for UDP specifies:
> 
> If the computed  checksum  is zero,  it is transmitted  as all ones
> (the equivalent  in one's complement  arithmetic).   An all zero
> transmitted checksum  value means that the transmitter  generated  no
> checksum  (for debugging or for higher level protocols that don't
> care).
> 
> RFC 793 for TCP has no such special treatment for the checksum of zero,
> but rte_ipv4_udptcp_cksum() implements the UDP special treatment
> anyway.


  reply	other threads:[~2020-05-15 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  1:27 [dpdk-dev] [PATCH] lib/librte_net: fix bug for ipv4 checksum calculating guohongzhi
2020-05-14 12:56 ` [dpdk-dev] [PATCH] lib/librte_net: fix bug for ipv4 checksumcalculating Morten Brørup
2020-05-14 14:19   ` Olivier Matz
2020-05-15  1:04   ` guohongzhi (A)
2020-05-15 10:03     ` Morten Brørup [this message]
2020-05-24 15:22 ` [dpdk-dev] [PATCH] lib/librte_net: fix bug for ipv4 checksum calculating Thomas Monjalon

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=98CBD80474FA8B44BF855DF32C47DC35C60FCB@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=chenchanghu@huawei.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=guohongzhi1@huawei.com \
    --cc=haifeng.lin@huawei.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=jiayu.hu@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=zhoujingbin@huawei.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).