Bug 1883562 - Unexpected behaviour of ovsdb *_is_new() functions
Summary: Unexpected behaviour of ovsdb *_is_new() functions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch2.13
Version: RHEL 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Mark Gray
QA Contact: qding
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-29 15:08 UTC by Mark Gray
Modified: 2021-05-20 19:30 UTC (History)
6 users (show)

Fixed In Version: openvswitch2.13-2.13.0-71.el8fdp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-20 19:29:38 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:2083 0 None None None 2021-05-20 19:30:00 UTC

Description Mark Gray 2020-09-29 15:08:23 UTC
Description of problem:

ovsdb-idlc.in is compiled with an ovsdb schema to build APIs to access ovsdb tables. ovsdb-idlc.in creates functions of the type *_is_new() using a template in ovsdb-idlc.in:

e.g.

static inline bool %(s)s_is_new(const struct %(s)s *row) 

becomes

ovsrec_interface_is_new()
sbrec_logical_flow_is_new()

The template definition for these functions is incorrect which may cause performance degradation or unexpected behaviour.

Comment 2 Timothy Redaelli 2021-03-16 14:14:13 UTC
openvswitch is openvswitch 2.9, moved to openvswitch 2.13
added also Fixed in Version (mandatory for a bug in MODIFIED status)

Comment 9 errata-xmlrpc 2021-05-20 19:29:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (openvswitch2.13 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2083


Note You need to log in before you can comment on or make changes to this bug.