summaryrefslogtreecommitdiff
path: root/ofproto/bond.c
diff options
context:
space:
mode:
authorGowrishankar Muthukrishnan <gmuthukr@redhat.com>2019-10-22 10:59:14 +0530
committerBen Pfaff <blp@ovn.org>2019-10-23 10:24:39 -0700
commit423416f58749de8e498afccc15d290a656abdf72 (patch)
treeb04e9aaeb38cdac77df7ebfbd84e1fcfccf46e3a /ofproto/bond.c
parent1051576cf2b8a6ffddf849d984c250a8456e6144 (diff)
downloadopenvswitch-423416f58749de8e498afccc15d290a656abdf72.tar.gz
lacp: report desync in ovs threads enabling slave
It is helpful in reporting main thread that is yet to enable bond slave, but link state was brought up by lacp thread and capture this desync between ovs threads for debugging. Fixes: a8448cb170 ("lacp: Avoid packet drop on LACP bond after link up") Signed-off-by: Gowrishankar Muthukrishnan <gmuthukr@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'ofproto/bond.c')
-rw-r--r--ofproto/bond.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/ofproto/bond.c b/ofproto/bond.c
index c5d5f2c03..3b148a244 100644
--- a/ofproto/bond.c
+++ b/ofproto/bond.c
@@ -817,6 +817,10 @@ bond_check_admissibility(struct bond *bond, const void *slave_,
* When may_enable is TRUE, it means LACP is UP and waiting for the
* main thread to run LACP state machine and enable the slave. */
verdict = (slave->enabled || slave->may_enable) ? BV_ACCEPT : BV_DROP;
+ if (!slave->enabled && slave->may_enable) {
+ VLOG_DBG_RL(&rl, "bond %s: slave %s: main thread not yet enabled slave",
+ bond->name, bond->active_slave->name);
+ }
goto out;
case LACP_CONFIGURED:
if (!bond->lacp_fallback_ab) {