ibmvnic: Process crqs after enabling interrupts
[ Upstream commit6e20d00158
] Soon after registering a CRQ it is possible that we get a fail over or maybe a CRQ_INIT from the VIOS while interrupts were disabled. Look for any such CRQs after enabling interrupts. Otherwise we can intermittently fail to bring up ibmvnic adapters during boot, specially in kexec/kdump kernels. Fixes:032c5e8284
("Driver for IBM System i/p VNIC protocol") Reported-by: Vaishnavi Bhat <vaish123@in.ibm.com> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com> Reviewed-by: Dany Madden <drt@linux.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
d1e4d44821
commit
9644f24424
|
@ -3835,6 +3835,9 @@ static int init_crq_queue(struct ibmvnic_adapter *adapter)
|
|||
crq->cur = 0;
|
||||
spin_lock_init(&crq->lock);
|
||||
|
||||
/* process any CRQs that were queued before we enabled interrupts */
|
||||
tasklet_schedule(&adapter->tasklet);
|
||||
|
||||
return retrc;
|
||||
|
||||
req_irq_failed:
|
||||
|
|
Loading…
Reference in New Issue