Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix access to an out-of-scope stack memory.

On 5/3/24 11:29, Eelco Chaudron wrote: > > > On 3 May 2024, at 1:36, Ilya Maximets wrote: > >> While tracing NAT actions, pointer to the action may be stored in the >> recirculation node for future reference. However, while translating >> actions for the group bucket in xlate_group_bucket, the

Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix access to an out-of-scope stack memory.

On 3 May 2024, at 1:36, Ilya Maximets wrote: > While tracing NAT actions, pointer to the action may be stored in the > recirculation node for future reference. However, while translating > actions for the group bucket in xlate_group_bucket, the action list is > allocated temporarily on stack.

Re: [ovs-dev] [PATCH] ofproto-dpif-trace: Fix access to an out-of-scope stack memory.

On 5/3/24 1:36 AM, Ilya Maximets wrote: While tracing NAT actions, pointer to the action may be stored in the recirculation node for future reference. However, while translating actions for the group bucket in xlate_group_bucket, the action list is allocated temporarily on stack. So, in

[ovs-dev] [PATCH] ofproto-dpif-trace: Fix access to an out-of-scope stack memory.

While tracing NAT actions, pointer to the action may be stored in the recirculation node for future reference. However, while translating actions for the group bucket in xlate_group_bucket, the action list is allocated temporarily on stack. So, in case the group translation leads to NAT, the