tapv2: deleting tap interface may leak buffers (VPP-1124) 22/10122/1
authorSteven <sluong@cisco.com>
Tue, 9 Jan 2018 19:13:29 +0000 (11:13 -0800)
committersteven luong <sluong@cisco.com>
Tue, 16 Jan 2018 16:59:18 +0000 (16:59 +0000)
commita624dbe7711a5852110a2cc28da1f72f5817708b
tree04f727fa8ed3955d0b306b6136671c81efff5c26
parent887ffb65fd9ce99db9a2ae0a3a1fa5456ba9b67c
tapv2: deleting tap interface may leak buffers (VPP-1124)

Buffers may be allocated for indirect descriptors by tx thread and
they are freed when tx thread is invoked in the next invocation.
This is to allow the recipient (kernel) to have a chance to process
them. But if the tap interface is deleted, the tx thread may not yet
be called to clean up the indirect descriptors' buffers. In that case,
we need to remove them without waiting for the tx thread to be called.
Failure to do so may cause buffers leak when the tap interface is deleted.

For the RX ring, leakage also exists for vring->buffers when the interface
is removed.

Change-Id: I3df313a0e60334776b19daf51a9f5bf20dfdc489
Signed-off-by: Steven <sluong@cisco.com>
(cherry picked from commit d8a998e74b815dd3725dfcd80080e4e540940236)
src/vnet/devices/tap/tap.c
src/vnet/devices/virtio/device.c
src/vnet/devices/virtio/virtio.c
src/vnet/devices/virtio/virtio.h