From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michal Kubecek <mkubecek@suse.cz>
Subject: Re: Linux 4.14 - regression: broken tun/tap / bridge network with
 virtio - bisected
Date: Mon, 27 Nov 2017 17:55:42 +0100
Message-ID: <20171127165541.fxijtjwtrdsjtqhg@unicorn.suse.cz>
References: <9615150a-eb78-2f9d-798f-6aa460932aec@01019freenet.de>
 <fc8cef7d-7b5a-d72a-9c31-5890fdac68c6@01019freenet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com
To: Andreas Hartmann <andihartmann@01019freenet.de>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mx2.suse.de ([195.135.220.15]:40945 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753351AbdK0Qzn (ORCPT <rfc822;netdev@vger.kernel.org>);
        Mon, 27 Nov 2017 11:55:43 -0500
Content-Disposition: inline
In-Reply-To: <fc8cef7d-7b5a-d72a-9c31-5890fdac68c6@01019freenet.de>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

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