linux-kernel - RE: Regression in hyperv network driver in 3.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25b90b45e3284715ab0ab00cb812a99f@BY2PR03MB299.namprd03.prod.outlook.com>
Date:	Tue, 27 May 2014 13:43:46 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Bernhard Walle <bernhard@...lle.de>,
	Haiyang Zhang <haiyangz@...rosoft.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Regression in hyperv network driver in 3.14


> -----Original Message-----
> From: Bernhard Walle [mailto:bernhard@...lle.de]
> Sent: Tuesday, May 27, 2014 4:10 AM
> To: Haiyang Zhang
> Cc: KY Srinivasan; linux-kernel@...r.kernel.org
> Subject: Regression in hyperv network driver in 3.14
> 
> Hello,
> 
> using a 3.14 kernel in a Linux VM running on HyperV (Windows Server 2008
> R2) we get following error:
> 
>    hv_netvsc: hv_netvsc channel opened successfully
>    hv_netvsc vmbus_0_9 (unregistered net_device): Unable to complete
> receive buffer initialization with NetVsp - status 2
>    hv_netvsc vmbus_0_9 (unregistered net_device): unable to connect to
> NetVSP - -22
>    hv_netvsc vmbus_0_9 (unregistered net_device): unable to add netvsc
> device (ret -22)
>    hv_netvsc: probe of vmbus_0_9 failed with error -22
> 
> Bisecting the problem shows that commit
> b679ef73edc251f6d200a7dd2396e9fef9e36fc3 is responsible. Reverting it
> fixes the issue. Even only changing NETVSC_RECEIVE_BUFFER_SIZE to 2M
> fixes the issue!
> 
> The virtual machine has 2 GiB of memory and 4 CPUs.
> 
> Can I provide more information to track down the problem?

This bug has been fixed upstream. The issue is with regards to the older hosts (ws2008 r2) not
Being able to handle the larger receive buffer currently used.

K. Y
> 
> 
> Regards,
> Bernhard

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/