From: Gert D. <ge...@gr...> - 2025-07-25 18:06:13
|
Thanks for that work. I tested all the "easy" notifications (DEL_PEER and FLOAT), and can confirm that the race/mixup we observed in gerrit#1086 (issue #793) is now fixed for good - with sufficient patience it's still possible to inject a FLOAT message between "ask for peer stats" and "receive peer stats", but the new dispatching logic handles things just fine, we're no longer losing FLOAT messages, and life is good. I did not test KEY_SWAP_NTF as that's not easy to trigger (without kernel changes to lower the threshold) but as that code is not affected at all by this commit I do not expect any surprises there. Besides the manual test, this handled the DCO client/server test runs just fine. There's some suggestions to the code I still have, but "it works, ship it" (so we get more exposure to the code we considered fixed) - the cleanup can be a separate patch. Your patch has been applied to the master branch. commit f353b7100c859a02e70723c998594c3efd83c419 Author: Antonio Quartulli Date: Fri Jul 25 19:27:02 2025 +0200 dco_linux: fix async message reception Signed-off-by: Antonio Quartulli <an...@ma...> Acked-by: Gert Doering <ge...@gr...> Message-Id: <202...@gr...> URL: https://www.mail-archive.com/ope...@li.../msg32339.html Signed-off-by: Gert Doering <ge...@gr...> -- kind regards, Gert Doering |