Branch: refs/heads/fixes
Home:
https://github.com/kronosnet/kronosnet
Commit: 78d00c88ed13a3e6eb11bfd4c940a6418a7d26d3
https://github.com/kronosnet/kronosnet/commit/78d00c88ed13a3e6eb11bfd4c940a…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2019-03-25 (Mon, 25 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: 07688a2afca385b11b87fc079ff888d2b02ff27b
https://github.com/kronosnet/kronosnet/commit/07688a2afca385b11b87fc079ff88…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2019-03-25 (Mon, 25 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/78d00c88ed13%5E...07688a2afc…