[ovs-discuss] one patch was omitted to be pushed to branch-2.3---datapath: Fix recirc bug where skb is double freed

Andy Zhou azhou at nicira.com
Tue Jun 16 05:34:47 UTC 2015


I was not able to reproduce the bug on my setup and did not find
anything obvious that will corrupt memory. I have not figured out what
I can do to narrow this down further.

Can you reliably reproduce it? If yes, will you be able to narrow it
down further at your end?

The following information may be tangentially useful:
Does this only happen on one kernel version?  If yes which one. Have
your tried more than one version of the kernel?
Any local changes to either Linux kernel or OVS?
Have you tried with more one distribution?


On Sat, Jun 13, 2015 at 11:33 PM, ZHANG Zhiming
<zhangzhiming at yunshan.net.cn> wrote:
> Hi, Andy,
>
> Do you need any other information to figure out this problem?
>
> ________________________________
> ZHANG Zhiming
> Yunshan Networks
>
> From: Andy Zhou
> Date: 2015-05-27 10:13
> To: zhangzhiming
> CC: Alex Wang; discuss
> Subject: Re: Re: [ovs-discuss] one patch was omitted to be pushed to
> branch-2.3---datapath: Fix recirc bug where skb is double freed
> On Sun, May 24, 2015 at 1:46 AM, ZHANG Zhiming
> <zhangzhiming at yunshan.net.cn> wrote:
>> Hi,
>>
>>
>> Here you are.
>> This bug is triggered by configuring bond_mode=banlace-tcp and lacp=active
>> simultaneously.
>> The version of OVS is 2.3.1.
>>
>>
>
> Thanks, this helps. The backtrace suggested there is a stack
> corruption from 'execute_recirc()',  But it not
> obvious what is the problem.  I will need to think about it more. In
> the mean time, would you please post
> a snap shot of the datapath flows,  using the 'ovs-dpctl dump-flows'
> command.
>
> Thanks,
>
> Andy



More information about the discuss mailing list