Re: [PATCH v2] virtio: Work around frames incorrectly marked as gso

2020-02-24 Thread Anton Ivanov
On 24/02/2020 12:46, Michael S. Tsirkin wrote: On Mon, Feb 24, 2020 at 10:19:12AM +, anton.iva...@cambridgegreys.com wrote: From: Anton Ivanov Some of the locally generated frames marked as GSO which arrive at virtio_net_hdr_from_skb() have no GSO_TYPE, no fragments (data_len = 0) and l

Re: [PATCH v2] virtio: Work around frames incorrectly marked as gso

2020-02-24 Thread Michael S. Tsirkin
On Mon, Feb 24, 2020 at 10:19:12AM +, anton.iva...@cambridgegreys.com wrote: > From: Anton Ivanov > > Some of the locally generated frames marked as GSO which > arrive at virtio_net_hdr_from_skb() have no GSO_TYPE, no > fragments (data_len = 0) and length significantly shorter > than the MTU

Re: [PATCH v2] virtio: Work around frames incorrectly marked as gso

2020-02-24 Thread kbuild test robot
Hi, I love your patch! Perhaps something to improve: [auto build test WARNING on vhost/linux-next] [also build test WARNING on linus/master ipvs/master v5.6-rc3 next-20200224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest t

[PATCH v2] virtio: Work around frames incorrectly marked as gso

2020-02-24 Thread anton . ivanov
From: Anton Ivanov Some of the locally generated frames marked as GSO which arrive at virtio_net_hdr_from_skb() have no GSO_TYPE, no fragments (data_len = 0) and length significantly shorter than the MTU (752 in my experiments). This is observed on raw sockets reading off vEth interfaces in all