From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from huawei.com (szxga01-in.huawei.com [45.249.212.187]) by dpdk.org (Postfix) with ESMTP id B34BE2B8C for ; Fri, 22 Feb 2019 08:34:09 +0100 (CET) Received: from DGGEMM405-HUB.china.huawei.com (unknown [172.30.72.56]) by Forcepoint Email with ESMTP id 0B03825D47FCE9E054E4; Fri, 22 Feb 2019 15:34:06 +0800 (CST) Received: from DGGEMM533-MBX.china.huawei.com ([169.254.5.181]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0415.000; Fri, 22 Feb 2019 15:33:56 +0800 From: wangyunjian To: "dev@dpdk.org" , "shahafs@mellanox.com" , "yskoh@mellanox.com" CC: xudingke , "Zhaohui (zhaohui, Polestar)" Thread-Topic: =?Windows-1252?Q?[dpdk-dev]_Segfault_when_eal_thread_executing_mlx5_nic?= =?Windows-1252?Q?=91s_lsc_event?= Thread-Index: AdTKepEq0LI+0ZL0SfmwRtoo2ksFCA== Date: Fri, 22 Feb 2019 07:33:56 +0000 Message-ID: <34EFBCA9F01B0748BEB6B629CE643AE60CA350AD@DGGEMM533-MBX.china.huawei.com> Accept-Language: en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.177.24.66] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [dpdk-dev] =?windows-1252?q?_Segfault_when_eal_thread_executing_m?= =?windows-1252?q?lx5_nic=91s_lsc_event?= X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 07:34:10 -0000 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 0x00007f54c9641237 in raise () from /usr/lib64/libc.so.6 #1 0x00007f54c9642928 in abort () from /usr/lib64/libc.so.6 #2 0x00000000006a8749 in PAT_abort () #3 0x00000000006a588d in patchIllInsHandler () #4 #5 0x00007f54c6acd2c8 in flow_list_destroy (dev=3Ddev@entry=3D0xad8940 , flow=3D0x1444b1b00, list=3D0x14455e618) at /usr/src/debug/dpdk-mlx4-pmd-18.11/drivers/net/mlx5/mlx5_flow.c:2150 #6 0x00007f54c6acfe1b in mlx5_flow_list_flush (dev=3D0xad8940 , list=3D0x14455e618) at /usr/src/debug/dpdk-mlx4-pmd-18.11/drive= rs/net/mlx5/mlx5_flow.c:2170 #7 0x00007f54c6ac5cc4 in mlx5_traffic_disable (dev=3D) at /u= sr/src/debug/dpdk-mlx4-pmd-18.11/drivers/net/mlx5/mlx5_trigger.c:384 #8 0x00007f54c6ac637d in mlx5_traffic_restart (dev=3D0xad8940 ) at /usr/src/debug/dpdk-mlx4-pmd-18.11/drivers/net/mlx5/mlx5_tri= gger.c:400 #9 0x00007f54d1db3bba in rte_eth_dev_default_mac_addr_set (port_id=3D, addr=3D0x140200f40) at /usr/src/debug/dpdk-18.11/lib/librte_ethd= ev/rte_ethdev.c:3230 #10 0x00007f54cd8dee81 in mac_address_slaves_update (bonded_eth_dev=3Dbonde= d_eth_dev@entry=3D0xad48c0 ) at /usr/src/debug/dpdk-18.11/= drivers/net/bonding/rte_eth_bond_pmd.c:1842 #11 0x00007f54cd8e0c31 in bond_ethdev_lsc_event_callback (port_id=3D, type=3D, param=3D, ret_param=3D) at /usr/src/debug/dpdk-18.11/drivers/net/bonding/rte_eth_bond_pmd.c:3070 #12 0x00007f54cd8e117b in bond_ethdev_slave_lsc_delay (cb_arg=3D0xad48c0 ) at /usr/src/debug/dpdk-18.11/drivers/net/bonding/rte_eth_b= ond_pmd.c:2298 #13 0x00007f54d25ebe5f in eal_alarm_callback (arg=3D) at /us= r/src/debug/dpdk-18.11/lib/librte_eal/linuxapp/eal/eal_alarm.c:90 #14 0x00007f54d25ea8aa in eal_intr_process_interrupts (nfds=3D, events=3D) at /usr/src/debug/dpdk-18.11/lib/librte_eal/l= inuxapp/eal/eal_interrupts.c:838 #15 eal_intr_handle_interrupts (totalfds=3D, pfd=3D21) at /u= sr/src/debug/dpdk-18.11/lib/librte_eal/linuxapp/eal/eal_interrupts.c:885 #16 eal_intr_thread_main (arg=3D) at /usr/src/debug/dpdk-18.= 11/lib/librte_eal/linuxapp/eal/eal_interrupts.c:965 #17 0x00007f54cade6dd5 in start_thread () from /usr/lib64/libpthread.so.0 #18 0x00007f54c970950d in clone () from /usr/lib64/libc.so.6