ibmvnic: Call napi_disable instead of napi_enable in failure path
authorNathan Fontenot <nfont@linux.vnet.ibm.com>
Wed, 24 May 2017 01:53:38 +0000 (21:53 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 17 Jun 2017 04:41:50 +0000 (06:41 +0200)
commit4544ba3173b7e4f15c8c921997847390e5652268
tree5fa56439879397cdc2c21f9a6406bd7ef2b0ce6b
parent74e24d1ea1a4fc8e1d4faa43263229aa45513cd3
ibmvnic: Call napi_disable instead of napi_enable in failure path

[ Upstream commit e722af6391949e8851310441bb0cec157d25611d ]

The failure path in ibmvnic_open() mistakenly makes a second call
to napi_enable instead of calling napi_disable. This can result
in a BUG_ON for any queues that were enabled in the previous call
to napi_enable.

Signed-off-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/net/ethernet/ibm/ibmvnic.c