Re: [ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-27 Thread Andy Zhou
On Mon, Sep 26, 2016 at 8:30 PM, Ben Pfaff wrote: > On Tue, Sep 20, 2016 at 01:27:08PM -0700, Andy Zhou wrote: > > The newly added replication logic makes it possible for a monitor to > > receive delete and insertion of the same row back to back, which > > was not possible before. Add logic (and

Re: [ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-26 Thread Ben Pfaff
I'm really puzzled about how this is getting to the list. d...@openvswitch.com bounces for me. I had to change it to dev@openvswitch.org to avoid that. I see that openvswitch.com is registered to the Linux Foundation though. ___ dev mailing list dev@ope

Re: [ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-26 Thread Ben Pfaff
On Tue, Sep 20, 2016 at 01:27:08PM -0700, Andy Zhou wrote: > The newly added replication logic makes it possible for a monitor to > receive delete and insertion of the same row back to back, which > was not possible before. Add logic (and comment) to handle this > case to avoid follow crash reporte

Re: [ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-20 Thread Andy Zhou
On Tue, Sep 20, 2016 at 4:39 PM, Joe Stringer wrote: > On 20 September 2016 at 13:27, Andy Zhou wrote: > > The newly added replication logic makes it possible for a monitor to > > receive delete and insertion of the same row back to back, which > > was not possible before. Add logic (and comment

Re: [ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-20 Thread Joe Stringer
On 20 September 2016 at 13:27, Andy Zhou wrote: > The newly added replication logic makes it possible for a monitor to > receive delete and insertion of the same row back to back, which > was not possible before. Add logic (and comment) to handle this > case to avoid follow crash reported by Valgr

[ovs-dev] [PATCH] OVSDB: Fix segfalut during replication.

2016-09-20 Thread Andy Zhou
The newly added replication logic makes it possible for a monitor to receive delete and insertion of the same row back to back, which was not possible before. Add logic (and comment) to handle this case to avoid follow crash reported by Valgrind: #0 0x00453edd in ovsdb_datum_compare_3