Re: Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected

From: Michal Kubecek <mkubecek@suse.cz>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com
Subject: Re: Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected
Date: Mon, 27 Nov 2017 17:55:42 +0100	[thread overview]
Message-ID: <20171127165541.fxijtjwtrdsjtqhg@unicorn.suse.cz> (raw)
In-Reply-To: <fc8cef7d-7b5a-d72a-9c31-5890fdac68c6@01019freenet.de>

On Mon, Nov 27, 2017 at 05:46:14PM +0100, Andreas Hartmann wrote:
> 
> Using virtio not just breaks the network completely as described above,
> it even leaves a never stoppable or restartable qemu process (even kill
> -9 doesn't work). It's absolutely necessary to *force* a reboot to exit
> or restart the VM.
> 
> I switched back to linux 4.13 as 4.14 virtualization is quite unusable.
> 
> I'm not the only one affected:
> https://bugzilla.kernel.org/show_bug.cgi?id=197861

What does stack trace of that process look like (/proc/$pid/stack)? Is
it similar to the stack trace from kernel.org bugzilla?

Michal Kubecek