From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: netdev@vger.kernel.org, saeedm@mellanox.com, edumazet@google.com
Subject: Re: [Patch net v2] mlx5: fixup checksum for short ethernet frame padding
Date: Mon, 03 Dec 2018 15:17:24 -0800 (PST) [thread overview]
Message-ID: <20181203.151724.648093455366632499.davem@davemloft.net> (raw)
In-Reply-To: <20181128061013.3885-1-xiyou.wangcong@gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Tue, 27 Nov 2018 22:10:13 -0800
> When an ethernet frame is padded to meet the minimum ethernet frame
> size, the padding octets are not covered by the hardware checksum.
> Fortunately the padding octets are ususally zero's, which don't affect
> checksum. However, we have a switch which pads non-zero octets, this
> causes kernel hardware checksum fault repeatedly.
>
> Prior to commit 88078d98d1bb ("net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends"),
> skb checksum is forced to be CHECKSUM_NONE when padding is detected.
> After it, we need to keep skb->csum updated, like what we do for FCS.
>
> The logic is a bit complicated when dealing with both FCS and padding,
> so I wrap it up in a helper function mlx5e_csum_padding().
>
> I tested this patch with RXFCS on and off, it works fine without any
> warning in both cases.
>
> Fixes: 88078d98d1bb ("net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends"),
> Cc: Saeed Mahameed <saeedm@mellanox.com>
> Cc: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Saeed, are you going to take care of this?
next prev parent reply other threads:[~2018-12-03 23:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 6:10 [Patch net v2] mlx5: fixup checksum for short ethernet frame padding Cong Wang
2018-11-28 15:00 ` Eric Dumazet
2018-11-28 22:16 ` Cong Wang
2018-11-28 23:50 ` Eric Dumazet
2018-11-28 23:57 ` Cong Wang
2018-11-29 0:05 ` Cong Wang
2018-11-29 0:14 ` Eric Dumazet
2018-11-30 0:03 ` Saeed Mahameed
2018-11-29 0:07 ` Eric Dumazet
2018-11-29 3:40 ` Cong Wang
2018-11-29 3:49 ` Eric Dumazet
2018-11-29 3:53 ` Cong Wang
2018-11-29 4:09 ` Eric Dumazet
2018-11-30 0:30 ` Saeed Mahameed
2018-12-03 23:17 ` David Miller [this message]
2018-12-03 23:45 ` Cong Wang
2018-12-04 19:21 ` Saeed Mahameed
2018-12-04 20:50 ` Cong Wang
2018-12-05 1:06 ` Saeed Mahameed
2018-12-05 2:15 ` Cong Wang
2018-12-13 8:40 ` Nikola Ciprich
2018-12-13 17:08 ` Saeed Mahameed
2018-12-14 9:33 ` Nikola Ciprich
2019-01-05 18:35 ` Nikola Ciprich
2019-01-06 11:10 ` Saeed Mahameed
2019-01-18 1:19 ` Christoph Paasch
2019-01-19 0:45 ` Saeed Mahameed
2019-01-22 11:35 ` David Laight
2018-12-05 2:52 ` Cong Wang
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=20181203.151724.648093455366632499.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=xiyou.wangcong@gmail.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).