Hello,

This is a resend of the series posted on 2026-10-16, with the patches
unchanged: my mail provider rewrapped the long lines of that posting,
so it does not apply.  Each patch is now attached whole (commit message
and diff) as text/plain.  The mail body holds only a From: line, so
that git am and patchwork keep the author, since the list rewrites the
>From of my mails.

These two patches fix the column counts of ovsdb-server monitor change
sets after a monitor condition adds a column that is not monitored, a
follow-up to commits 469e98e16db1 and e0f42d4a6548.

Patch 1 updates the change set that tracks new changes, which kept the
old number of columns and was then filled with rows lacking the new
column.  Patch 2 makes the V1 update path use the change set's number
of columns, as the update2 path already does.

Each patch adds a test to tests/ovsdb-monitor.at.  With
AddressSanitizer, the first and third new tests fail on the current
code and pass with the series; the second checks monitor_cond_since
from a transaction before the column was added.

Please apply the patches as they are (git am), so that they keep their
author; change anything you like in review.

Alejandro Pacheco (2):
  ovsdb: monitor: Update new change set column counts.
  ovsdb: monitor: Use change set column count for V1 updates.

 ovsdb/monitor.c        |  24 ++++-
 tests/ovsdb-monitor.at | 216 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 238 insertions(+), 2 deletions(-)

--
Alejandro Pacheco
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to