n_xportp@entry=0x7fadfef93e90)
>>> at ofproto/ofproto-dpif-xlate.c:1550
>>> #2 0x7fae029fba23 in xlate_normal (ctx=0x7fadfef94420) at
>>> ofproto/ofproto-dpif-xlate.c:2339
>>> #3 xlate_output_action (ctx=ctx@entry=0x7fadfef94420, port=>> out>,
entry=0x7fadfefb3178) at ofproto/ofproto-dpif-xlate.c:5272
> > #6 0x7fae029f16f6 in upcall_xlate (wc=0x7fadfefb31d0,
> > odp_actions=0x7fadfefb3190, upcall=0x7fadfefb3120, udpif=0x7fae03a4fb60) at
> > ofproto/ofproto-dpif-upcall.c:1068
> > #7 process_upcall (udpif
e03a7e7b8) at
> ofproto/ofproto-dpif-upcall.c:696
> #10 0x7fae02a7e596 in ovsthread_wrapper (aux_=) at
> lib/ovs-thread.c:340
> #11 0x7fae01d14dc5 in start_thread () from /usr/lib64/libpthread.so.0
> #12 0x7fae0132271d in clone () from /usr/lib64/libc.so.6
> (gdb) p xport
ian <wangyunj...@huawei.com>
> Cc: b...@ovn.org; d...@openvswitch.org; caihe <ca...@huawei.com>; Huangjian
> (J) <huangjian.huangj...@huawei.com>
> Subject: Re: [ovs-dev] [BUG] upcall handler thread crash
>
> Hi, what’s the OvS version you tested. I didn’t get the
Hi, what’s the OvS version you tested. I didn’t get the crash with master
version.
The test script is described as below.
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth1
for i in `seq 0 1000`;
do
ovs-vsctl add-port br0 eth2
ovs-vsctl del-port br0 eth2
done
Thanks.
Nick
> On Feb 4,
