@Assaf, it isn't clear from your comment - can you no longer reproduce with the specified patch (hinting it might fix it), or even without the specified patch (something else changed)?
Also, I added Kuba as a subscriber - IIRC he worked on the whole get_root_helper_child_pid (or something around that neighborhood) and might be able to provide a "why this was implemented like this". I'm thinking about if that function always return the child pid, this should popped up a lot sooner (ie. ovs agent with ip monitor, l3 agent with keepalived...)
Perhaps the cause isn't get_root_helper_child_pid, but the way linuxbridge spawn new processes?
@Assaf, it isn't clear from your comment - can you no longer reproduce with the specified patch (hinting it might fix it), or even without the specified patch (something else changed)?
Also, I added Kuba as a subscriber - IIRC he worked on the whole get_root_ helper_ child_pid (or something around that neighborhood) and might be able to provide a "why this was implemented like this". I'm thinking about if that function always return the child pid, this should popped up a lot sooner (ie. ovs agent with ip monitor, l3 agent with keepalived...)
Perhaps the cause isn't get_root_ helper_ child_pid, but the way linuxbridge spawn new processes?