Bug #7856
closeddpdk: EAL options defined in suricata.yaml are not accepted at startup
Description
Suricata in DPDK run mode can configure the DPDK Environment Abstraction Layer (EAL) using the dpdk.eal-params option defined in suricata.yaml. The commit 4dfd44d changed how the EAL options are parsed and effectively disabled passing the parameters to the rte_eal_init() function. The issue was caused by decreasing the size argument passed to strlcat in AllocAndSetOption within runmode-dpdk.c, trancating every option by one character. The fix was to revert to the original approach by adding + 1 to the size.
Updated by Adam Kiripolsky 2 months ago
- Status changed from In Progress to Resolved
Updated by Lukas Sismis 2 months ago
- Status changed from Resolved to Closed
To Adam -- when your ticket is merged (not staged to merge), please link the PR and close the ticket.
Merged: https://github.com/OISF/suricata/pull/13737
Thank you!
Updated by Lukas Sismis 2 months ago
To add:
We use state Resolved only for tickets that need to be backported to the older versions; each ticket is for a specific version only.
So you have 2 tickets regarding the same issue. You first need to merge into master branch, you set your master-targetting ticket as resolved, you merge the cherry-picked (from the master branch) backport to e.g., suricata-v7 branch, and then you can close both tickets linking the respective PRs.
Updated by Philippe Antoine about 1 month ago
- Target version changed from 8.0.2 to 8.0.1
Updated by Victor Julien about 1 month ago
- Subject changed from DPDK EAL options defined in suricata.yaml are not accepted by suricata during startup to dpdk: EAL options defined in suricata.yaml are not accepted at startup