From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: drbd-utils v9.29.0
Date: Tue, 29 Oct 2024 13:45:12 +0100 [thread overview]
Message-ID: <ZyDY2E5rNLAujqNG@arm64> (raw)
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Dear DRBD users,
this is version 9.29.0 of drbd-utils. We did not find any bug since RC1.
for your convenience the announcement of RC1:
It contains many fixes and improvements ranging from fixed segfaults,
fixed undefined behavior, fixes for bugs that only triggered on arm64 to
improvements for our systemd templates and new features in drbdmon. If
you have not been bitten by any of the bugs, there is no too urgent need
to upgrade, still, the fixes and improvements are worth it.
Regards, rck
GIT: https://github.com/LINBIT/drbd-utils/commit/28e2ab938fe5e99fdcb27c0c393a9f2a3fb8fdee
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-utils-9.29.0.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack
Changelog:
9.29.0
-----------
* drbdmeta: fix initialization for external md
* build: allow disabling keyutils
* tests: export sanitized environment
* drbdmon: various improvements
* build: add cyclonedx
* drbsetup,v9: fix multiple paths drbdsetup show --json
strictly speaking breaking change, but maily used internally
* events2: expose if device is open
* drbdadm: fix undefined behavior that triggered on amd64
* shared: fix out-of-bounds access in parsing
* drbsetup,v9: event consistency with peer devices
* drbdadm: fix parsing of v8.4 configs for compatibility
* drbdmeta: fix segfault for check-resize on intentionally diskless
* drbd-promote@.service: check if ExecCondition is available
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-10-29 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZyDY2E5rNLAujqNG@arm64 \
--to=roland.kammerer@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox