Re: [ovs-dev] [BUG][revalidator] ovs crash and could NOT fix again after set request_mtu

2024-06-10 Thread Adrián Moreno
On Mon, Jun 03, 2024 at 10:18:05AM GMT, Simon Jones wrote: > In ovs code, bridge_reconfigure function should ONLY be called in > ovs-vswitchd thread. > > But how about this case: > - ovs-vswitchd is starting, the ovs-vswitch thread calls bridge_reconfigure > function. > - at the same time,

Re: [ovs-dev] [BUG][revalidator] ovs crash and could NOT fix again after set request_mtu

2024-06-02 Thread Simon Jones
In ovs code, bridge_reconfigure function should ONLY be called in ovs-vswitchd thread. But how about this case: - ovs-vswitchd is starting, the ovs-vswitch thread calls bridge_reconfigure function. - at the same time, ovs-vsctl set port xxx request_mtu=4800 comes to ovs-vswitchd thread. - the

Re: [ovs-dev] [BUG][revalidator] ovs crash and could NOT fix again after set request_mtu

2024-05-31 Thread Ilya Maximets
On 5/31/24 04:00, Simon Jones wrote: > Hi all, > > I'm using ovs-dpdk(ovs:2.17.1, dpdk:21.11.1). > Now I found a BUG that ovs crash and could NOT fix again after set > request_mtu. > > 1. How to reproduce and my Analysis: > ``` > # start ovs and add bridge and port and openflow > > [root@bogon

[ovs-dev] [BUG][revalidator] ovs crash and could NOT fix again after set request_mtu

2024-05-30 Thread Simon Jones
Hi all, I'm using ovs-dpdk(ovs:2.17.1, dpdk:21.11.1). Now I found a BUG that ovs crash and could NOT fix again after set request_mtu. 1. How to reproduce and my Analysis: ``` # start ovs and add bridge and port and openflow [root@bogon ~]# ovs-vsctl show 0444869c-dc4d-462f-8caf-074ecbab1a55