Project

General

Profile

Actions
Copy link

Bug #5936

closed
LS LS

Task #5965: tracking: Improving DPDK capture interface and docs

dpdk: Release mempool only after the device closes

Bug #5936: dpdk: Release mempool only after the device closes

Added by Lukas Sismis about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Sismis
Target version:
7.0.0-rc2
Affected Versions:
Effort:
Difficulty:
Label:

Description

Can lead to segfault when the device driver tries to empty the mbufs to a release mempool.

VJ Updated by Victor Julien about 3 years ago Actions
Copy link
 #1

Is this related to #5619 ?

LS Updated by Lukas Sismis about 3 years ago Actions
Copy link
 #2

Likely yes, I reproduced this while trying out Suricata in VMs. Now, this should be fixed and E1000, VMXNET3, and virtio-net drivers work. But I can't seem to try Suricata with multiple queues on those interfaces.

LS Updated by Lukas Sismis about 3 years ago Actions
Copy link
 #3

  • Status changed from New to In Progress

LS Updated by Lukas Sismis about 3 years ago Actions
Copy link
 #4

  • Status changed from In Progress to In Review

LS Updated by Lukas Sismis about 3 years ago Actions
Copy link
 #5

  • Parent task set to #5965

LS Updated by Lukas Sismis almost 3 years ago Actions
Copy link
 #6

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: PDF Atom