path: root/drivers
diff options
authorThomas Falcon <tlfalcon@linux.vnet.ibm.com>2018-02-09 11:41:09 -0600
committerDavid S. Miller <davem@davemloft.net>2018-02-09 14:20:39 -0500
commitfaefaa97215a0c05105d7ae180fe1a3b5979ad1f (patch)
tree05ec5c9be1529f7b919e0ddb50c38160062dca7c /drivers
parent437a4db66df3bc9f139cfbfc66913ea207d9162a (diff)
ibmvnic: Reset long term map ID counter
When allocating RX or TX buffer pools, the driver needs to provide a unique mapping ID to firmware for each pool. This value is assigned using a counter which is incremented after a new pool is created. The ID can be an integer ranging from 1-255. When migrating to a device that requests a different number of queues, this value was not being reset properly. As a result, after enough migrations, the counter exceeded the upper bound and pool creation failed. This is fixed by resetting the counter to one in this case. Signed-off-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/ethernet/ibm/ibmvnic.c b/drivers/net/ethernet/ibm/ibmvnic.c
index dd4a2946e1da..ce127a72cda2 100644
--- a/drivers/net/ethernet/ibm/ibmvnic.c
+++ b/drivers/net/ethernet/ibm/ibmvnic.c
@@ -1644,6 +1644,7 @@ static int do_reset(struct ibmvnic_adapter *adapter,
return rc;
} else if (adapter->req_rx_queues != old_num_rx_queues ||
adapter->req_tx_queues != old_num_tx_queues) {
+ adapter->map_id = 1;

Privacy Policy