Displaying 18 results from an estimated 18 matches for "10273661".
2020 Feb 11
5
[PATCH] virtio: Work around frames incorrectly marked as gso
...UML vector network
> drivers.
>
I think we need to find the culprit and fix it there, lots of other things
can break otherwise.
Just printing out skb->dev->name should do the trick, no?
> --
> Anton R. Ivanov
> Cambridgegreys Limited. Registered in England. Company Number 10273661
> https://www.cambridgegreys.com/
2020 Feb 11
5
[PATCH] virtio: Work around frames incorrectly marked as gso
...UML vector network
> drivers.
>
I think we need to find the culprit and fix it there, lots of other things
can break otherwise.
Just printing out skb->dev->name should do the trick, no?
> --
> Anton R. Ivanov
> Cambridgegreys Limited. Registered in England. Company Number 10273661
> https://www.cambridgegreys.com/
2020 Feb 12
1
[PATCH] virtio: Work around frames incorrectly marked as gso
...> Brgds,
ok if it's veth then you need to add a similar printk patch to veth
and re-run to see where does it come from originally.
> >
> >
> >
> > > --
> > > Anton R. Ivanov
> > > Cambridgegreys Limited. Registered in England. Company Number 10273661
> > > https://www.cambridgegreys.com/
> >
> >
> > _______________________________________________
> > linux-um mailing list
> > linux-um at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-um
> >
>
> --
> Anto...
2020 Feb 13
4
[PATCH] virtio: Work around frames incorrectly marked as gso
...traffic is locally originated on the host.
>
> A,
OK so is it code in __tcp_transmit_skb that sets gso_size to non-null
when gso_type is 0?
> >
> >
> > > --
> > > Anton R. Ivanov
> > > Cambridgegreys Limited. Registered in England. Company Number 10273661
> > > https://www.cambridgegreys.com/
> >
> >
> > _______________________________________________
> > linux-um mailing list
> > linux-um at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-um
> >
>
> --
> Anto...
2020 Feb 13
4
[PATCH] virtio: Work around frames incorrectly marked as gso
...traffic is locally originated on the host.
>
> A,
OK so is it code in __tcp_transmit_skb that sets gso_size to non-null
when gso_type is 0?
> >
> >
> > > --
> > > Anton R. Ivanov
> > > Cambridgegreys Limited. Registered in England. Company Number 10273661
> > > https://www.cambridgegreys.com/
> >
> >
> > _______________________________________________
> > linux-um mailing list
> > linux-um at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-um
> >
>
> --
> Anto...
2020 Feb 13
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...it_skb that sets gso_size to non-null
> when gso_type is 0?
It does look like that, but I cannot see it when reading it :(
>
>
>>>
>>>
>>>> --
>>>> Anton R. Ivanov
>>>> Cambridgegreys Limited. Registered in England. Company Number 10273661
>>>> https://www.cambridgegreys.com/
>>>
>>>
>>> _______________________________________________
>>> linux-um mailing list
>>> linux-um at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-um
>>>
>...
2020 Feb 12
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...probably normal for a locally originated frame.
I cannot reproduce this with network traffic by the way - it happens only if the traffic is locally originated on the host.
A,
>
>
>> --
>> Anton R. Ivanov
>> Cambridgegreys Limited. Registered in England. Company Number 10273661
>> https://www.cambridgegreys.com/
>
>
> _______________________________________________
> linux-um mailing list
> linux-um at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in Englan...
2020 Feb 12
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...uld be veth - the test is over a vEth pair and all frames are locally originated by iperf.
In practice - I will retest and post the results sometimes later today.
Brgds,
>
>
>
>> --
>> Anton R. Ivanov
>> Cambridgegreys Limited. Registered in England. Company Number 10273661
>> https://www.cambridgegreys.com/
>
>
> _______________________________________________
> linux-um mailing list
> linux-um at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in Englan...
2020 Feb 11
2
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/11 ??12:55, Anton Ivanov wrote:
>
>
> On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
>> From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
>>
>> Some of the 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
2020 Feb 11
2
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/11 ??12:55, Anton Ivanov wrote:
>
>
> On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
>> From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
>>
>> Some of the 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
2020 Feb 13
3
[PATCH] virtio: Work around frames incorrectly marked as gso
On Thu, Feb 13, 2020 at 07:44:06AM -0800, Eric Dumazet wrote:
>
>
> On 2/13/20 2:00 AM, Michael S. Tsirkin wrote:
> > On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
> >>
> >>
> >> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> >>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> >>>> On
2020 Feb 13
3
[PATCH] virtio: Work around frames incorrectly marked as gso
On Thu, Feb 13, 2020 at 07:44:06AM -0800, Eric Dumazet wrote:
>
>
> On 2/13/20 2:00 AM, Michael S. Tsirkin wrote:
> > On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
> >>
> >>
> >> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> >>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> >>>> On
2020 Feb 10
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...pe = VIRTIO_NET_HDR_GSO_NONE;
> + else
> + return -EINVAL;
> + }
> if (sinfo->gso_type & SKB_GSO_TCP_ECN)
> hdr->gso_type |= VIRTIO_NET_HDR_GSO_ECN;
> } else
>
ping.
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
2020 Feb 11
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...t gso_type is not? Looks like a bug
> elsewhere.
>
> Thanks
>
>
Yes.
I could not trace it where it is coming from.
I see it when doing recvmmsg on raw sockets in the UML vector network
drivers.
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
2020 Feb 13
0
[PATCH] virtio: Work around frames incorrectly marked as gso
...these packets.
A.
>
> ?
>
>
> _______________________________________________
> linux-um mailing list
> linux-um at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
2019 Dec 09
3
[PATCH] virtio: Work around frames incorrectly marked as gso
From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
Some of the 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 4.x and 5.x kernels I tested.
These frames are reported as invalid while
2020 Feb 13
1
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/13 ??1:38, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
>>> On 11/02/2020 02:51, Jason Wang wrote:
>>>>
>>>> On 2020/2/11 ??12:55, Anton Ivanov wrote:
>>>>>
>>>>>
>>>>> On 09/12/2019 10:48, anton.ivanov
2019 May 22
1
custom virt-io support (in user-mode-linux)
On 22/05/2019 14:02, Johannes Berg wrote:
> Hi,
>
> While my main interest is mostly in UML right now [1] I've CC'ed the
> qemu and virtualization lists because something similar might actually
> apply to other types of virtualization.
>
> I'm thinking about adding virt-io support to UML, but the tricky part is
> that while I want to use the virt-io basics