[dpdk-dev] Segfault when eal thread executing mlx5 nic‘s lsc event

+ rte_rwlock_write_lock(&priv->flows_rwlock); mlx5_flow_list_flush(dev, &priv->ctrl_flows); + rte_rwlock_write_unlock(&priv->flows_rwlock); rte_errno = ret; /* Restore rte_errno. */ return -rte_errno; } @@ -380,8 +389,9 @@ mlx5_traffic_disable(struct rte_eth_dev *dev) { struct priv *priv = dev->data->dev_private; - + rte_rwlock_write_lock(&priv->flows_rwlock); mlx5_flow_list_flush(dev, &priv->ctrl_flows); + rte_rwlock_write_unlock(&priv->flows_rwlock); } -邮件原件- 发件人: wangyunjian 发送时间: 2019年2月22日 15:34 收件人: dev@dpdk.org; shah...@mellanox.com; ys...@mellanox.com 抄送: xudingke ; Zhaohui (zhaohui, Polestar) 主题: [dpdk-dev] Segfault when eal thread executing mlx5 nic‘s lsc event

Re: [dpdk-dev] Segfault when eal thread executing mlx5 nic‘s lsc event

Hi Yunjian, Wednesday, March 6, 2019 5:06 AM, Zhaohui (zhaohui, Polestar): > Subject: [dpdk-dev] Segfault when eal thread executing mlx5 nic‘s lsc event > > Hi: > I think the flow list may be accessed in the same time by two different > threads and may cause some errors. Do it

[dpdk-dev] Segfault when eal thread executing mlx5 nic‘s lsc event

I think the flow list may be accessed in the same time by two different threads and may cause some errors. Do it need a lock to protect the flow list? Thanks Yunjian (gdb) bt #0 0x7f54c9641237 in raise () from /usr/lib64/libc.so.6 #1 0x7f54c9642928 in abort () from /usr/lib64/li