On Mon, Aug 10, 2020 at 10:59 PM Tonghao Zhang wrote:
>
> On Tue, Aug 11, 2020 at 12:08 PM Cong Wang wrote:
> >
> > On Mon, Aug 10, 2020 at 8:27 PM Tonghao Zhang
> > wrote:
> > >
> > > On Tue, Aug 11, 2020 at 10:24 AM Cong Wang
> > > wrote:
> > > >
> > > > On Mon, Aug 10, 2020 at 6:16 PM Tong
w:
> >
> > On Fri, Aug 7, 2020 at 11:32 AM Johan Knöös wrote:
> > >
> > > On Tue, Aug 4, 2020 at 8:52 AM Gregory Rose wrote:
> > > >
> > > >
> > > >
> > > > On 8/3/2020 12:01 PM, Johan Knöös via discuss wrote:
> > &g
On Tue, Aug 4, 2020 at 8:52 AM Gregory Rose wrote:
>
>
>
> On 8/3/2020 12:01 PM, Johan Knöös via discuss wrote:
> > Hi Open vSwitch contributors,
> >
> > We have found openvswitch is causing double-freeing of memory. The
> > issue was not present in ker
Hi Open vSwitch contributors,
We have found openvswitch is causing double-freeing of memory. The
issue was not present in kernel version 5.5.17 but is present in
5.6.14 and newer kernels.
After reverting the RCU commits below for debugging, enabling
slub_debug, lockdep, and KASAN, we see the warn
