Please don't drop the list.
The difference between x.y.0 and x.y.z is always just bug fixes. The
commit log describes what changed, e.g.
https://github.com/openvswitch/ovs/commits/branch-2.4
On Fri, Jul 15, 2016 at 08:36:57AM -0600, gavin_rema...@selinc.com wrote:
> Thanks.
>
> Is there an easy way to find a list of bug fixes between releases?
>
> We are near releasing a product and can't just upgrade. How do I find out
> that you discovered and fixed a bug? How can I see if there are others we
> need to address?
>
> Thank you.
>
>
>
> From: Ben Pfaff <b...@ovn.org>
> To: gavin_rema...@selinc.com
> Cc: discuss@openvswitch.org
> Date: 07/14/2016 06:01 PM
> Subject: Re: [ovs-discuss] Meter config memory allocation problem
>
>
>
> On Wed, Jul 13, 2016 at 01:31:02PM -0600, gavin_rema...@selinc.com wrote:
> > We are using OVS v2.4.0 and seem to have discovered a memory allocation
> > issue.
> >
> > When we have more than 41 meters (each with a single Band) defined, we
> > regularly get corruption in meters 42 and beyond within a Meter
> > Configuration Response to a request with meter_id=ALL.
> >
> > ofpmp_init() is used as part of the message handling in ofproto.c
> > (handle_meter_request). It calls ofpraw_alloc_stats_reply, allocating
> > 1000 "tail" bytes. Since each Meter requires 24 bytes in the message
> and
> > 24 * 41 = 984, this seems to be the issue we are encountering. It looks
>
> > like Meters 42 and beyond occupy memory that we do not own.
> >
> > Is this function being used properly with a Meter Configuration request?
>
> > Why the hard-coded 1000 bytes of space?
> >
> > We need to fix this ASAP. We can do so, but an official patch would be
> > better.
>
> This was fixed in OVS 2.4.1. Please upgrade.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
