9f44dd3d8a
It's possible that while waiting for the spinlock, another
entity (that owns the spinlock) has shut down the admin queue.
If it then attempts to use the queue, it will panic.
It adds a check for this condition on the receive side. This
matches an existing check on the send queue side.
Fixes:
|
||
---|---|---|
.. | ||
crypto | ||
net | ||
Makefile |