Branch: refs/heads/stable1-proposed Home: https://github.com/kronosnet/kronosnet Commit: 1137b71f57e998a344c8f5db5135b3c28097d587 https://github.com/kronosnet/kronosnet/commit/1137b71f57e998a344c8f5db5135b… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2019-03-26 (Tue, 26 Mar 2019) Changed paths: M kronosnet.spec.in Log Message: ----------- [tests] test rpm should match currently installed version of libknet Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com> Commit: a9ca6afa22fe52d048059a2e63f60a97e87747fa https://github.com/kronosnet/kronosnet/commit/a9ca6afa22fe52d048059a2e63f60… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2019-03-26 (Tue, 26 Mar 2019) Changed paths: M libknet/transport_sctp.c M libknet/transport_udp.c Log Message: ----------- [transports] fix usage after free of transport info memory spotted while implementing functional testing for rekey. when configuring multiple hosts (3+) with 1 link sharing the same listener, but NOT enabling the link, if the user attempts to shutdown knet_h, the first call to knet_link_clear_config will not recognize that the listener is still in use by another link and will release all resources. At the time of invoking clear_config on the second link, transport_clear_config will access already freed memory, or alternatively, a call to link_enable would cause a crash because the listener does no longer exist. Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com> Compare: https://github.com/kronosnet/kronosnet/compare/2e29e0bbc8d6...a9ca6afa22fe