- Mar 02, 2025
-
-
Ferenc Wágner authored
-
Ferenc Wágner authored
Upstream commit 8d46eb01 added version info to several already exported symbols. (It also removed a couple of names from the version scripts, but that part does not change the export lists since the respective symbols have long been removed from the libraries.) Since the new versions are also the default versions when resolving unversioned references, applications linked against the old Corosync libraries will find the new versioned symbols, so this change does not break the ABI.
- Jan 04, 2025
-
-
Ferenc Wágner authored
-
Ferenc Wágner authored
-
Ferenc Wágner authored
Update to upstream version '3.1.9' with Debian dir b808b9d13196c7fe1709d75e84452115f3a07edc
-
- Oct 31, 2024
-
-
Christine Caulfield authored
Updating to Rust 2021 is a no-op (but worth doing for future), I've also taken this opportunity to use the latest bitflags crate. Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
Christine Caulfield authored
Previously, orf_token_tx was only incremented on initial send, this is obviously wrong and resulted in the TX count being significantly lower than any RX count. Now we increment it every time the ORF token is sent or resent. As a quick test, on a single node system the RX and TX stats will now match. Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- Oct 23, 2024
-
-
Jan Friesse authored
Function message_handler_orf_token contains extra debug info enabled by defining GIVEINFO. Insted of using long long unsigned int use better suited uint64_t and make use of QB_TIME_NS_IN_MSEC constant instead of hardcoded number. Also compile tv_old conditionally so it is not used by accident. Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
Jan Friesse authored
Timestamp diff is very unlikely to be larger than 32-bit integer but it is still worth to use 64-bit. Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
Jan Friesse authored
Token rx and tx timestamps were computed and stored as 32-bit unsigned integer but substracted in other parts of code from 64-bit integer. Result was, that node with uptime larger than 49.71 days (2^32/(1000*60*60*24)) reported wrong numbers for stats.srp.time_since_token_last_received and in log message during long pause (function timer_function_orf_token_warning). Solution is to store rx and tx data as 64-bit integer. Fixes #761 Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
- Sep 19, 2024
-
-
Christine Caulfield authored
Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- Sep 02, 2024
-
-
Jan Friesse authored
If strdup of kv_item key or value failed only kv_item itself was freed. Free also key and value (kv_item is zeroed so free of NULL variable is safe). Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
Jan Friesse authored
Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
Jan Friesse authored
new_config interfaces was freed on success, but not if some previous configuration step failed. Solution is to move free of interfaces to same point as where orig_interfaces are freed. Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
- Aug 07, 2024
-
-
Alexander Aring authored
This patch adds support to change the default corosync pid file lock path. This is useful to run corosync net namespace environment only and since the pid lock file cannot be clarified over the conf because the pid lock file exists before config parsing we allow the user to specify it over the command line. Signed-off-by:
Alexander Aring <aahringo@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- Aug 05, 2024
-
-
Jan Friesse authored
Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
Jan Friesse authored
As suggested by Christine Caulfield split long sentence so now paragraph follows same formatting style as other options hopefully making it less confusing. Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Christine Caulfield <ccaulfie@redhat.com>
-
- Jul 20, 2024
-
-
Ferenc Wágner authored
This reverts commit a836090e. Now dh_installsystemd handles service files under /usr/lib correctly, so let DEP17 (Improve situation around aliasing effects from /usr-merge) proceed by moving our service files to /usr/lib/systemd/system. Closes: #1073683
- Jul 04, 2024
-
-
Christine Caulfield authored
Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
Christine Caulfield authored
The big change here is that all API calls now take a &Handle rather than making a copy. This, apart from being more sensible and efficient, allows us to implment Drop on the handle so that it will call _free() when it goes out of scope. There's some jiggery-pokery with a clone flag in there now because of callbacks that can return a valid handle, and we want those to be Drop'ed sensibly. Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- May 28, 2024
-
-
Ferenc Wágner authored
As per dbus-daemon(1): > Third-party packages would historically install XML files into > /etc/dbus-1/system.d, but this practice is now considered to be > deprecated: that directory should be treated as reserved for the > system administrator. Signed-off-by:
Ferenc Wágner <wferi@debian.org> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- May 26, 2024
-
-
Ferenc Wágner authored
-
Ferenc Wágner authored
-
Ferenc Wágner authored
-
Ferenc Wágner authored
- May 25, 2024
-
-
Ferenc Wágner authored
-
Ferenc Wágner authored
The lsb-base package is used by the init scripts, which are only run by sysv-rc, which has already depended on lsb-base since bullseye.
-
Ferenc Wágner authored
-
Ferenc Wágner authored
-
Ferenc Wágner authored
Update to upstream version '3.1.8' with Debian dir 0fe0eb81025c8bb97977789541717b065a720369
-
- May 02, 2024
-
-
xin liang authored
- Add default value 5405 for mcastport - Add brief introduction for UDP/UDPU/KNET transport - Keep format consistent (use uppercase) for above 3 transport types Signed-off-by:
xin liang <xliang@suse.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- Mar 12, 2024
-
-
Jan Friesse authored
Link Corosync project archived copy of Yair Amir's PhD thesis and paper about totem protocol. Signed-off-by:
Jan Friesse <jfriesse@redhat.com> Reviewed-by:
Fabio M. Di Nitto <fdinitto@redhat.com>
-
- Feb 05, 2024
-
-
Christine Caulfield authored
Because crypto changing happens in the 'commit' phase of the reload and we can't get sure that knet will allow the new parameters, the result gets ignored. This can happen in FIPS mode if a non-FIPS cipher is requested. This patch reports the errors back in a cmap key so that the command-line can spot those errors and report them back to the user. It also restores the internal values for crypto so that subsequent attempts to change things have predictable results. Otherwise further attempts can do nothing but not report any errors back. I've also added some error reporting back for the knet ping counters using this mechanism. The alternative to all of this would be to check for FIPS in totemconfig.c and then exclude certain options, but this would be duplicating code that could easily get out of sync. This system could also be a useful mechanism for reporting back other 'impossible' errors. Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Jan Friesse <jfriesse@redhat.com>
-
- Jan 02, 2024
-
-
Christine Caulfield authored
I've only added missing symbols and removed old ones. The actual library version numbers might need assessing too. Signed-off-by:
Christine Caulfield <ccaulfie@redhat.com> Reviewed-by:
Fabio M. Di Nitto <fdinitto@redhat.com>
-