[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171108.103105.142249724388345463.davem@davemloft.net>
Date: Wed, 08 Nov 2017 10:31:05 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: vkuznets@...hat.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devel@...uxdriverproject.org, kys@...rosoft.com,
haiyangz@...rosoft.com, sthemmin@...rosoft.com,
eric.dumazet@...il.com
Subject: Re: [PATCH net-next v2 0/2] hv_netvsc: fix a hang on channel/mtu
changes
From: Vitaly Kuznetsov <vkuznets@...hat.com>
Date: Thu, 2 Nov 2017 11:35:29 +0100
> It was found that netvsc driver doesn't survive e.g.
>
> # while true; do ethtool -L eth0 combined 4; ethtool -L eth0 combined 8; done"
>
> test. I was able to identify a hang in guest/host communication, it is
> fixed by PATCH1 of this series. PATCH2 is a cosmetic change masking
> unneeded messages.
>
> Changes since v1:
> - Throw away patches 2 and 3 of the original series as one is unneeded and
> the other is not justified [Eric Dumazet, Stephen Hemminger] so I'm only
> fixing the hang now, the crash doesn't reproduce. Will keep an eye on it.
Series applied to net-next, thank you.
Powered by blists - more mailing lists