Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix infinite recirculation tracing.

On 2/26/24 14:10, Simon Horman wrote: > On Thu, Feb 22, 2024 at 04:06:32PM +0100, Ilya Maximets wrote: >> Trace attempts to process all the recirculations. However, if there >> is a recirculation loop, i.e. if every recirculation generates another >> recirculation, this process will never stop.

Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix infinite recirculation tracing.

On Thu, Feb 22, 2024 at 04:06:32PM +0100, Ilya Maximets wrote: > Trace attempts to process all the recirculations. However, if there > is a recirculation loop, i.e. if every recirculation generates another > recirculation, this process will never stop. It will grind until the > trace fills the

Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix infinite recirculation tracing.

On 2/22/24 16:46, Jaime Caamaño Ruiz wrote: > We have the option to tweak the ct action ct_state output with `*--ct-next* > /flags/ ` trace > option. > Would it make sense to have the same capability for the ip_frag field given > that >

Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix infinite recirculation tracing.

We have the option to tweak the ct action ct_state output with `*--ct-next* *flags* ` trace option. Would it make sense to have the same capability for the ip_frag field given that the ct action might influence its value after re-injection?

[ovs-dev] [PATCH] ofproto-dpif-trace: Fix infinite recirculation tracing.

Trace attempts to process all the recirculations. However, if there is a recirculation loop, i.e. if every recirculation generates another recirculation, this process will never stop. It will grind until the trace fills the system memory. A simple reproducer: make sandbox ovs-vsctl add-br