public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: virtualization@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: cristian.marussi@arm.com, "Jason Wang" <jasowang@redhat.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>
Subject: Re: [REGRESSION] Virtio networking issues on v6.17-rc1
Date: Wed, 13 Aug 2025 19:09:24 +0100	[thread overview]
Message-ID: <aJzU1JsV5we-QqgQ@pluto> (raw)
In-Reply-To: <aJycJvs3xztfD5Rm@pluto>

On Wed, Aug 13, 2025 at 03:07:34PM +0100, Cristian Marussi wrote:
> Hi,
> 

Hi,

> Not sure if it has been already reported but in a kvmtool/guest setup moving
> the guest kernel from v6.16 to v6.17-rc1 I completely lost host-guest network
> functionality....in a very funny way, though, I'd say...
> 
> In fact NO error is apparently reported in the guest kernel log and the
> interfaces seems perfectly up an running both sides, but looking at the
> host/guest interfaces you can see that ALL received frames are indeed dropped:
> 
> 
> enp0s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> ....
>         ether 02:15:15:15:15:15  txqueuelen 1000  (Ethernet)           <<<<<<<<<<<<<<<<
>         RX packets 125  bytes 17948 (17.5 KiB)
>         RX errors 0  dropped 125 overruns 0  frame 0
>         TX packets 1207  bytes 51182 (49.9 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 
> ...on the host same..(taken later on...)
> 
> tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.33.1  netmask 255.255.255.0  broadcast 192.168.33.255
>         ether 8a:10:f6:df:a1:70  txqueuelen 1000  (Ethernet)
>         RX packets 804  bytes 43904 (42.8 KiB)
>         RX errors 0  dropped 804  overruns 0  frame 0
>         TX packets 101  bytes 14408 (14.0 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> ....and for a good reason, apparently, since sniffing around on the Host TAP
> interface I can see a never ending stream of:
> 
> $ sudo tcpdump -i tap0
> listening on tap0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
> 22:40:42.309158 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00 (oui Ethernet), ethertype Unknown (0xffff), length 54:
> 	0x0000:  ffff ffff 0215 1515 1515 0806 0001 0800  ................       <<<<<<<<<<<<<
> 	0x0010:  0604 0001 0215 1515 1515 c0a8 2102 0000  ............!...
> 	0x0020:  0000 0000 c0a8 2101                      ......!.
> 
> ... DST/SRC Macs are just all zeros WHILE in the payload you can spot my guest
> SRC mac address 0215 1515 1515  :P
>

I bisected this regression to:

56a06bd40fab64448aa6b84aa06b3dc470c1254a is the first bad commit

commit 56a06bd40fab64448aa6b84aa06b3dc470c1254a
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Tue Jul 8 17:55:02 2025 +0200

    virtio_net: enable gso over UDP tunnel support.
    
    If the related virtio feature is set, enable transmission and reception
    of gso over UDP tunnel packets.
    
    Most of the work is done by the previously introduced helper, just need
    to determine the UDP tunnel features inside the virtio_net_hdr and
    update accordingly the virtio net hdr size.
    
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>

 drivers/net/virtio_net.c | 85 ++++++++++++++++++++++++++++++++++++------------

Reverting this commit on top of v6.17-rc1 solves for me and network works fine again.

Thanks,
Cristian

  reply	other threads:[~2025-08-13 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 14:07 [REGRESSION] Virtio networking issues on v6.17-rc1 Cristian Marussi
2025-08-13 18:09 ` Cristian Marussi [this message]
2025-08-13 19:51   ` Paolo Abeni
2025-08-13 20:31     ` Cristian Marussi
2025-08-13 20:41       ` Paolo Abeni
2025-08-13 21:04         ` Cristian Marussi
2025-08-14 15:40         ` Paolo Abeni

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=aJzU1JsV5we-QqgQ@pluto \
    --to=cristian.marussi@arm.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mst@redhat.com \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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