From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Paweł Staszewski" <pstaszewski@itcare.pl>,
"Dimitris Michailidis" <dmichail@google.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Latest net-next kernel 4.19.0+
Date: Tue, 30 Oct 2018 07:16:18 -0700 [thread overview]
Message-ID: <76dfbbda-d7f1-b13a-5921-c12c3b0f8e3e@gmail.com> (raw)
In-Reply-To: <b0a36d1f-5518-392c-d731-1ec66ec48f92@itcare.pl>
On 10/30/2018 01:09 AM, Paweł Staszewski wrote:
>
>
> W dniu 30.10.2018 o 08:29, Eric Dumazet pisze:
>>
>> On 10/29/2018 11:09 PM, Dimitris Michailidis wrote:
>>
>>> Indeed this is a bug. I would expect it to produce frequent errors
>>> though as many odd-length
>>> packets would trigger it. Do you have RXFCS? Regardless, how
>>> frequently do you see the problem?
>>>
>> Old kernels (before 88078d98d1bb) were simply resetting ip_summed to CHECKSUM_NONE
>>
>> And before your fix (commit d55bef5059dd057bd), mlx5 bug was canceling the bug you fixed.
>>
>> So we now need to also fix mlx5.
>>
>> And of course use skb_header_pointer() in mlx5e_get_fcs() as I mentioned earlier,
>> plus __get_unaligned_cpu32() as you hinted.
>>
>>
>>
>>
>
> No RXFCS
>
> And this trace is rly frequently like once per 3/4 seconds
> like below:
> [28965.776864] vlan1490: hw csum failure
Might be vlan related.
Can you first check this :
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_rx.c b/drivers/net/ethernet/mellanox/mlx5/core/en_rx.c
index 94224c22ecc310a87b6715051e335446f29bec03..6f4bfebf0d9a3ae7567062abb3ea6532b3aaf3d6 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_rx.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_rx.c
@@ -789,13 +789,8 @@ static inline void mlx5e_handle_csum(struct net_device *netdev,
skb->ip_summed = CHECKSUM_COMPLETE;
skb->csum = csum_unfold((__force __sum16)cqe->check_sum);
if (network_depth > ETH_HLEN)
- /* CQE csum is calculated from the IP header and does
- * not cover VLAN headers (if present). This will add
- * the checksum manually.
- */
- skb->csum = csum_partial(skb->data + ETH_HLEN,
- network_depth - ETH_HLEN,
- skb->csum);
+ /* Temporary debugging */
+ skb->ip_summed = CHECKSUM_NONE;
if (unlikely(netdev->features & NETIF_F_RXFCS))
skb->csum = csum_add(skb->csum,
(__force __wsum)mlx5e_get_fcs(skb));
next prev parent reply other threads:[~2018-10-30 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 0:10 Latest net-next kernel 4.19.0+ Paweł Staszewski
2018-10-30 0:11 ` Paweł Staszewski
2018-10-30 0:34 ` Paweł Staszewski
2018-10-30 2:27 ` Cong Wang
2018-10-30 2:43 ` Cong Wang
2018-10-30 2:53 ` Eric Dumazet
2018-10-30 3:52 ` Eric Dumazet
2018-10-30 6:09 ` Dimitris Michailidis
2018-10-30 7:29 ` Eric Dumazet
2018-10-30 8:09 ` Paweł Staszewski
2018-10-30 14:16 ` Eric Dumazet [this message]
2018-10-30 17:32 ` Cong Wang
2018-10-30 17:50 ` Eric Dumazet
2018-10-30 17:54 ` Cong Wang
2018-10-31 21:05 ` Saeed Mahameed
2018-10-31 21:17 ` Cong Wang
2018-11-01 22:59 ` Paweł Staszewski
2018-11-08 18:35 ` Cong Wang
2018-10-31 21:22 ` Paweł Staszewski
2018-10-31 21:24 ` Paweł Staszewski
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=76dfbbda-d7f1-b13a-5921-c12c3b0f8e3e@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=dmichail@google.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
--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).