[dpdk-dev] [Bug 404] i40e: "i40e_res_pool_free(): Failed to find entry" error when rte_flow are flushed

[dpdk-dev] [Bug 404] i40e: "i40e_res_pool_free(): Failed to find entry" error when rte_flow are flushed

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=404

            Bug ID: 404
           Summary: i40e: "i40e_res_pool_free(): Failed to find entry"
                    error when rte_flow are flushed
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: maxime.leroy@6wind.com
  Target Milestone: ---

With dpdk master (commit id d0e160a00233), I got the following error when I try
to flush a rte_flow a second time (i.e. create a flow, delete, recreate and
then delete).

./build/app/testpmd  --legacy-mem     -c 1f -n 4 -w 0000:85:00.1 -- -i --rxq=1
--txq=1 --total-num-mbufs=10000
EAL: Detected 40 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Static memory layout is selected, amount of reserved memory can be
adjusted with -m or --socket-mem
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:85:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1583 net_i40e
EAL:   using IOMMU type 1 (Type 1)
Interactive-mode selected
...
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 179 / end
actions queue index 0 / end
Flow rule #0 created
testpmd> flow flush 0
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 179 / end
actions queue index 0 / end
Flow rule #0 created
testpmd> flow flush 0
i40e_res_pool_free(): Failed to find entry
testpmd> 

The error happens in i40e_res_pool_free:

 4951│         /* Not find, return */
 4952│         if (valid_entry == NULL) {
 4953├>                PMD_DRV_LOG(ERR, "Failed to find entry");
 4954│                 return -EINVAL;
 4955│         }
 4956│



(gdb) bt
#0  i40e_res_pool_free (pool=0x112c3fe510, base=0) at
/root/dpdk/drivers/net/i40e/i40e_ethdev.c:4953
#1  0x000055718b6fa489 in i40e_vsi_release (vsi=0x20015ab80) at
/root/dpdk/drivers/net/i40e/i40e_ethdev.c:5426
#2  0x000055718b8c6c8c in i40e_fdir_teardown (pf=0x112c3fe4f8) at
/root/dpdk/drivers/net/i40e/i40e_fdir.c:286
#3  0x000055718b97dc8e in i40e_flow_flush_fdir_filter (pf=0x112c3fe4f8) at
/root/dpdk/drivers/net/i40e/i40e_flow.c:5186
#4  0x000055718b97da24 in i40e_flow_flush (dev=0x55718e4e9300
<rte_eth_devices>, error=0x7fffd7360320) at
/root/dpdk/drivers/net/i40e/i40e_flow.c:5114
#5  0x000055718acc91dc in rte_flow_flush (port_id=0, error=0x7fffd7360320) at
/root/dpdk/lib/librte_ethdev/rte_flow.c:412
..

-- 
You are receiving this mail because:
You are the assignee for the bug.