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

2019-12-09 Thread anton . ivanov
From: Anton Ivanov 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

[PATCH v2 1/5] iommu: Implement iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Implement a generic function for removing reserved regions. This can be used by drivers that don't do anything fancy with these regions other than allocating memory for them. Signed-off-by: Thierry Reding --- drivers/iommu/iommu.c | 19 +++

[PATCH v2 2/5] iommu: arm: Use iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Use the new standard function instead of open-coding it. Cc: Will Deacon Cc: Robin Murphy Signed-off-by: Thierry Reding --- drivers/iommu/arm-smmu-v3.c | 11 +-- drivers/iommu/arm-smmu.c| 11 +-- 2 files changed, 2 insertions(+), 20 deletions(-)

[PATCH v2 4/5] iommu: intel: Use iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Use the new standard function instead of open-coding it. Cc: David Woodhouse Signed-off-by: Thierry Reding --- drivers/iommu/intel-iommu.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/iommu/intel-iommu.c

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

2019-12-09 Thread Johannes Berg
> else if (sinfo->gso_type & SKB_GSO_TCPV6) > hdr->gso_type = VIRTIO_NET_HDR_GSO_TCPV6; > - else > - return -EINVAL; > + else { > + if (skb->data_len == 0) > +

[PATCH v2 3/5] iommu: amd: Use iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Use the new standard function instead of open-coding it. Signed-off-by: Thierry Reding --- drivers/iommu/amd_iommu.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c index

[PATCH v2 0/5] iommu: Implement iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Most IOMMU drivers only need to free the memory allocated for each reserved region. Instead of open-coding the loop to do this in each driver, extract the code into a common function that can be used by all these drivers. Changes in v2: - change subject prefix to "iommu:

[PATCH v2 5/5] iommu: virtio: Use iommu_put_resv_regions_simple()

2019-12-09 Thread Thierry Reding
From: Thierry Reding Use the new standard function instead of open-coding it. Cc: Jean-Philippe Brucker Cc: virtualization@lists.linux-foundation.org Signed-off-by: Thierry Reding --- Changes in v2: - change subject prefix to 'iommu: virt:' to 'iommu: virtio:' drivers/iommu/virtio-iommu.c |

[PATCH net-next v9 0/3] netdev: ndo_tx_timeout cleanup

2019-12-09 Thread Michael S. Tsirkin
A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other

[PATCH net-next v9 3/3] netronome: use the new txqueue timeout argument

2019-12-09 Thread Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin Acked-by: Jakub Kicinski --- drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_common.c

Re: [PATCH net-next v9 1/3] netdev: pass the stuck queue to the timeout handler

2019-12-09 Thread Nathan Chancellor
Hi Michael, On Mon, Dec 09, 2019 at 11:29:03AM -0500, Michael S. Tsirkin wrote: > This allows incrementing the correct timeout statistic without any mess. > Down the road, devices can learn to reset just the specific queue. > > The patch was generated with the following script: > > > where

Re: [PATCH net-next v9 0/3] netdev: ndo_tx_timeout cleanup

2019-12-09 Thread David Miller
From: "Michael S. Tsirkin" Date: Mon, 9 Dec 2019 11:28:57 -0500 > A bunch of drivers want to know which tx queue triggered a timeout, > and virtio wants to do the same. > We actually have the info to hand, let's just pass it on to drivers. > Note: tested with an experimental virtio patch by