mirror of
https://github.com/opnsense/src.git
synced 2026-04-23 23:28:37 -04:00
f0d8d352c0
The netmap_rx_irq() function normally wakes up user-space threads waiting for more packets. In this case, it is not necessary to call it under the driver queue lock. However, if the interface is attached to a VALE switch, netmap_rx_irq() ends up calling rxsync on the interface (see netmap_bwrap_intr_notify()). Although concurrent rxsyncs are serialized through the kring lock (see nm_kr_tryget()), the lock acquire operation is not blocking. As a result, it may happen that netmap_rx_irq() is called on an RX ring while another instance is running, causing the second call to fail, and received packets stall in the receive VQ. We fix this issue by calling netmap_irx_irq() under the VQ lock. MFC after: 1 week |
||
|---|---|---|
| .. | ||
| balloon | ||
| block | ||
| console | ||
| mmio | ||
| network | ||
| pci | ||
| random | ||
| scsi | ||
| virtio.c | ||
| virtio.h | ||
| virtio_bus_if.m | ||
| virtio_config.h | ||
| virtio_ids.h | ||
| virtio_if.m | ||
| virtio_ring.h | ||
| virtqueue.c | ||
| virtqueue.h | ||