Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-06 Thread wangyunjian via dev
> -Original Message- > From: Ilya Maximets [mailto:i.maxim...@ovn.org] > Sent: Saturday, May 6, 2023 12:15 AM > To: wangyunjian ; d...@openvswitch.org > Cc: i.maxim...@ovn.org; luyicai > Subject: Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free wh

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-05 Thread Ilya Maximets
t;> Sent: Thursday, May 4, 2023 7:44 PM >>>> To: wangyunjian ; d...@openvswitch.org >>>> Cc: i.maxim...@ovn.org; luyicai >>>> Subject: Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free >>>> when xlate_actions(). >>>> >>&

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-04 Thread wangyunjian via dev
> -Original Message- > From: Ilya Maximets [mailto:i.maxim...@ovn.org] > Sent: Thursday, May 4, 2023 8:32 PM > To: wangyunjian ; d...@openvswitch.org > Cc: i.maxim...@ovn.org; luyicai > Subject: Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free wh

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-04 Thread Ilya Maximets
ubject: Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when >> xlate_actions(). >> >> On 4/19/23 08:29, Yunjian Wang wrote: >>> Currently, bundle->cvlans and xbundle->cvlans are pointing to the same >>> memory location. This can cause issues if t

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-04 Thread wangyunjian via dev
> -Original Message- > From: Ilya Maximets [mailto:i.maxim...@ovn.org] > Sent: Thursday, May 4, 2023 7:44 PM > To: wangyunjian ; d...@openvswitch.org > Cc: i.maxim...@ovn.org; luyicai > Subject: Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free wh

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-05-04 Thread Ilya Maximets
On 4/19/23 08:29, Yunjian Wang wrote: > Currently, bundle->cvlans and xbundle->cvlans are pointing to the > same memory location. This can cause issues if the main thread > modifies bundle->cvlans and frees it while the revalidator thread > is still accessing xbundle->cvlans. This can result in use

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-04-26 Thread Simon Horman
On Mon, Apr 24, 2023 at 02:06:53PM +0200, Ilya Maximets wrote: > On 4/23/23 05:47, wangyunjian wrote: > > Is there any issue with this patch? Why is it in the Superseded state? > > Hi. Not sure what happened here. > I moved it back to 'New' for now. That might have been me conflating things. If

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-04-26 Thread Simon Horman
On Wed, Apr 19, 2023 at 02:29:11PM +0800, Yunjian Wang via dev wrote: > Currently, bundle->cvlans and xbundle->cvlans are pointing to the > same memory location. This can cause issues if the main thread > modifies bundle->cvlans and frees it while the revalidator thread > is still accessing xbundle

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-04-24 Thread Ilya Maximets
t; Sent: Wednesday, April 19, 2023 2:29 PM >> To: d...@openvswitch.org; i.maxim...@ovn.org >> Cc: luyicai ; wangyunjian >> Subject: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when >> xlate_actions(). >> >> Currently, bundle->cvlans and xbundle-&

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-04-22 Thread wangyunjian via dev
Is there any issue with this patch? Why is it in the Superseded state? > -Original Message- > From: wangyunjian > Sent: Wednesday, April 19, 2023 2:29 PM > To: d...@openvswitch.org; i.maxim...@ovn.org > Cc: luyicai ; wangyunjian > Subject: [ovs-dev] [PATCH] ofproto-d

[ovs-dev] [PATCH] ofproto-dpif-xlate: Fix use-after-free when xlate_actions().

2023-04-18 Thread Yunjian Wang via dev
Currently, bundle->cvlans and xbundle->cvlans are pointing to the same memory location. This can cause issues if the main thread modifies bundle->cvlans and frees it while the revalidator thread is still accessing xbundle->cvlans. This can result in use after free errors. AddressSanitizer: heap-us