From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linux.dev
Subject: drbd-9.2.20 and drbd-9.3.4
Date: Tue, 15 Sep 2026 22:32:51 +0200 [thread overview]
Message-ID: <8633vajlvw.fsf@linbit.com> (raw)
Hi,
This is an unusual release. This time, we fixed more issues than in
any previous development cycle. This is because the team has used
ClaudeCode since the start of the Year. It took about half a year,
from our first experiments with it, to get to the point where we can
do much more in a cycle than before.
It helps extract the important needle from a haystack of loglines. It
also helps us write reproducers super quickly using our testing
framework. It enabled us to create new static analyzers tailored for
DRBD. It enabled us to create a simulator that lets us test the DRBD
code deterministically against unusual timings that are very hard to
reproduce on regular VMs.
Last but not least, it is much quicker than a human at coming up with
patch proposals. Even if you have to reject three, you may be
impressed by the solution when you review the fourth proposal.
I recommend upgrading to this version because of the number of fixes it
includes.
PS: I plan to discontinue the 9.2.x series soon. Expect only one more
release. We can’t wait to start the 9.4 series with exciting new
features. Maintaining 3 branches in parallel would be too much.
9.3.4 (api:genl2/proto:86-101,118-125/transport:22)
--------
* Fix drbdsetup failing with "Operation not supported" on every command
that names a peer; a regression of the YNL-generated netlink code in
9.3.4-rc.1
* Generate the netlink interface code with the upstream YNL generator
instead of the genl_magic macro system
* Fix a ProtocolError disconnect loop ("BAD! BarrierAck received with
n_writes=...") when two volumes of one connection replicate and
resync without replication at the same time
* Tolerate a verify-alg mismatch when connecting, and refuse to start
an online verify while the algorithms differ, instead of rejecting
the connection outright
* Fix several bitmap lifetime bugs around attach and detach: a NULL
bitmap dereference in the peer device statistics, a missing bitmap
in drbd_set_sync(), concurrent drbd_bm_free() callers, and freeing
a bitmap that a later attach published
* Fix a device reference leak and a NULL pointer dereference when a
peer request's bio allocation fails under memory pressure
* Hold state_rwlock while walking the transfer log from debugfs
* All fixes from 9.2.20
- Fix a secondary that stayed with the primary ending up Outdated for
good after an isolated peer returns: an equal-UUID reconcile is now
sourced from the node that has a primary neighbour
- Fix two nodes ending UpToDate with different data after a reconnect
with equal current UUIDs and out-of-sync bits standing: such bits now
survive a resync-free connect and drive a reconciliation resync
- Fix divergence around the end of a resync
- Fix a node losing its obligation to start a new data generation and
ending in a split brain
- Fix a number of aspects of online resize
- Fix a sync target overwriting acknowledged writes with older resync
data when the sync source lost the diskless primary; such writes are
now held back or postponed (new feature flag WRITE_POSTPONE) instead
of being silently rolled back
- Fix data corruption when a peer bitmap that is being cleared by a
running resync was copied for a second peer
- Fix several ways a Primary lost its obligation to start a new data
generation after losing a peer, each ending in silent divergence,
and a spurious I/O error when a deferred generation resumes; the
obligation is now tracked per volume and logged
- Fix a diskless Primary losing a peer: rotate the current UUID so the
stale peer resyncs on return, outdate far-away members before
resuming I/O, and keep the sole UpToDate survivor UpToDate; also
fixes promotions freezing I/O on nodes not connected to every member
- Fix a resync target ending with stale data or an old data generation
when a crashed primary rejoins or a diskless primary announces a new
generation mid-resync
- Fix al-updates=no: honour it at attach time, and mark all bitmap
slots out of sync after a primary crash
- Fix kernel memory corruption by a malicious or man-in-the-middle
peer sending out-of-range payload, drain or digest sizes, and a
divide error caused by bogus peer block sizes
- Fix a use-after-free of the resource when a connections dump is
interrupted, and a refcount imbalance flooding the log with put_ldev
assertions after a resync request allocation failure
- Fix soft lockups: the sender thread pinning a CPU while its
connection is down, and IRQ-disabled bitmap scans on multi-TiB
volumes
- Fix several deadlocks and hangs: whole-bitmap IO vs clear_peer_slot()
or online resize, WFBitMapS on an equal-UUID reconnect with leftover
out-of-sync bits, demotion starved by a failing connect handshake,
and connection teardown blocked behind an unacknowledged resync
conflict
- Fix many two-phase-commit issues: stale replies answering the wrong
transaction, prepared peers that disconnected, forwarding node
handling, a state_sem leak on timeout, and unbounded connect
retries; log which volume a connect is waiting for
- Fix resyncs stalling short of completion, and a connection dropping
to StandAlone when a crashed primary rejoins during a resync
- Fix drbd_suspend_io() not waiting for in-flight writes; a detach
hanging on a dead backing device stays interruptible
- Fix restoring quorum after a reboot when the remaining members are
diskless
- Fix connection losses: online resize ending in ProtocolError,
volume-less connections reconnecting every ping-timeout, lb-tcp
"drbdadm down" stalling for a connect-int, and a TLS control socket
close going unnoticed
- Declare a connection broken where a two-phase-commit send failed,
and repeat a disconnect without delay and with a bound; together
they end a hanging "drbdadm disconnect"
- Do not account requests as waiting for the activity log while it is
suspended; the stale counters throttled resync to c-min-rate and
drained the epoch for every incoming peer write
https://pkg.linbit.com//downloads/drbd/9/drbd-9.3.4.tar.gz
https://github.com/LINBIT/drbd/commit/e59b287b199f7224468af85b68a10e83c68213f5
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.20.tar.gz
https://github.com/LINBIT/drbd/commit/1b4ee6780a6072d423b05e8424438dd187fb0b99
best regards,
Phil
reply other threads:[~2026-09-15 20:32 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=8633vajlvw.fsf@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-announce@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.