[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68f25a28-b79e-d3ae-6eef-50c354ad63ae@gmail.com>
Date: Tue, 30 Oct 2018 00:29:13 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dimitris Michailidis <dmichail@...gle.com>
Cc: Cong Wang <xiyou.wangcong@...il.com>,
Paweł Staszewski <pstaszewski@...are.pl>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: Latest net-next kernel 4.19.0+
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.
Powered by blists - more mailing lists