Incorrect resultCode handling in PD callbacks
I reviewed this issue against the current PD callback implementation. The reported behavior could not be confirmed as a general missing-error propagation problem. Receive callbacks only run for applicable receive events; parameter, memory and socket errors generally occur on paths where no corresponding sample is delivered. For sending, pfCbFunction is documented as a pre-send callback (TRDP User's Manual, section 8.9.5). Therefore the callback cannot report the result of the subsequent socket send....
Lock-order inversion during topology counter update from TTI callback
No separate PD and pull/reply sequence counters in callbacks
Incomplete check in vos_netIfUp for DSA switch attached interfaces
Verified via code review
Test application to change topocounter (emulate ETB gateway)
MD reply/add listener does not use send parameters