| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: drbd-kmp-default | Distribution: SUSE Linux Enterprise 15 |
| Version: 9.1.16_k6.4.0_150600.21 | Vendor: SUSE LLC <https://www.suse.com/> |
| Release: 150600.3.18 | Build date: Thu May 16 22:04:41 2024 |
| Group: Unspecified | Build host: s390zp38 |
| Size: 1265656 | Source RPM: drbd-9.1.16-150600.3.18.src.rpm |
| Packager: https://www.suse.com/ | |
| Url: https://drbd.linbit.com/ | |
| Summary: Kernel driver | |
This module is the kernel-dependent driver for DRBD. This is split out so that multiple kernel driver versions can be installed, one for each installed kernel.
GPL-2.0-or-later
* Wed Jan 10 2024 [email protected]
- drbd fails to build with the latest 6.4 kernel of the week (bsc#1218658)
* Add patch
+ 0006-drbd-log-numeric-value-of-drbd_state_rv-as-well-as-s.patch
+ 0011-compat-block-pass-a-gendisk-to-open.patch
+ 0013-drbd-remove-unused-extern-for-conn_try_outdate_peer.patch
+ 0014-drbd-include-source-of-state-change-in-log.patch
+ 0015-compat-block-use-the-holder-as-indication-for-exclus.patch
+ 0018-drbd-rework-autopromote.patch
+ 0019-compat-block-remove-the-unused-mode-argument-to-rele.patch
+ 0022-compat-block-replace-fmode_t-with-a-block-specific-t.patch
+ 0023-compat-genetlink-remove-userhdr-from-struct-genl_inf.patch
* Wed Nov 08 2023 [email protected]
- drbd failed to build after 15sp6/dolomit updated kernel (bsc#1216666)
* Add patch
+ bsc-1216666-compat-sock-Remove-sendpage-in-favour-of-sendmsg-MSG.patch
* Tue Oct 31 2023 [email protected]
- drbd failed to build after 15sp6/dolomit updated kernel (bsc#1216666)
* Add patch
+ 0008-compat-block-introduce-holder-ops.patch
* Mon Sep 04 2023 [email protected]
- Update DRBD version from 9.0.30+ to 9.1.16 (jsc#PED-6362)
* 9.1.16 (api:genl2/proto:86-121/transport:18)
* shorten times DRBD keeps IRQs on one CPU disabled. Could lead
to connection interruption under specific conditions
* fix a corner case where resync did not start after resync-pause
state flapped
* fix online adding of volumes/minors to an already connected resource
* fix a possible split-brain situation with quorum enabled with
ping-timeout set to (unusual) high value
* fix a locking problem that could lead to kernel OOPS
* ensure resync can continue (bitmap-based) after interruption
also when it started as a full-resync first
* correctly handle meta-data when forgetting diskless peers
* fix a possibility of getting a split-brain although quorum enabled
* correctly propagate UUIDs after resync following a resize operation.
Consequence could be a full resync instead of a bitmap-based one
* fix a rare race condition that can cause a drbd device to end up
with WFBitMapS/Established replication states
* 9.1.15 (api:genl2/proto:86-121/transport:18)
* fix how flush requests are marked when submitted to the Linux IO
stack on the secondary node
* when establishing a connection failed with a two-pc timeout, a
receiver thread deadlocked, causing drbdsetup calls to block on
that resource (difficult to trigger)
* fixed a NULL-ptr deref (a OOPS) caused by a rare race condition
while taking a resource down
* fix a possible hard kernel-lockup, can only be triggerd when a
CPU-mask is configured
* updated kernel compatibility to at least Linux head and also fixed
a bug in the compat checks/rules that caused OOPSes of the previous
drbd releases when compiled with Linux-6.2 (or on RHEL 9.2 kernel).
* fix an aspect of the data-generation (UUID) handling where DRBD
failed to do a resync when a diskless node in the remaining
partition promotes and demotes while a diskful node is isolated
* fix an aspect of the data-generation (UUID) handling where DRBD
considered a node to have unrelated data; this bug was triggered by
a sequence involving removing two nodes from a cluster and readding
one with the "day-0" UUIDs.
* do not block specific state changes (promote, demote, attach, and
detach) when only some nodes add a new minor
* 9.1.14 (api:genl2/proto:86-121/transport:18)
* fix a race with concurrent promotion and demotion, which can
lead to an unexpected "split-brain" later on
* fix a specific case where promotion was allowed where it should not
* fix a race condition between auto-promote and a second two-phase
commit that can lead to a DRBD thread locking up in an endless loop
* fix several bugs with "resync-after":
- missing resync-resume when minor numbers run in opposite
direction as the resync-after dependencies
- a race that might lead to an OOPS in add_timer()
* fix an OOPS when reading from in_flight_summary in debugfs
* fix a race that might lead to an endless loop of printing
"postponing start_resync" while starting a resync
* fix diskless node with a diskfull with a 4KiB backend
* simplify remembering two-pc parents, maybe fixing a one-time-seen bug
* derive abort_local_transaction timeout from ping-timeout
* 9.1.13 (api:genl2/proto:86-121/transport:18)
* when calculating if a partition has quorum, take into account if
the missing nodes might have quorum
* fix forget-peer for diskless peers
* clear the resync_again counter upon disconnect
* also call the unfence handler when no resync happens
* do not set bitmap bits when attaching to an up-to-date disk (late)
* work on bringing the out-of-tree DRBD9 closer to DRBD in the upstream
kernel; Use lru_cahche.ko from the installed kernel whenever possible
* 9.1.12 (api:genl2/proto:86-121/transport:18)
* fix a race that could result in connection attempts getting aborted
with the message "sock_recvmsg returned -11"
* rate limit messages in case the peer can not write the backing storage
and it does not finish the necessary state transitions
* reduced the receive timeout during connecting to the intended 5 seconds
(ten times ping-ack timeout)
* losing the connection at a specific point in time during establishing
a connection could cause a transition to StandAlone; fixed that, so
that it keeps trying to connect
* fix a race that could lead to a fence-peer handler being called
unexpectedly when the fencing policy is changed at the moment before
promoting
* 9.1.11 (api:genl2/proto:86-121/transport:18)
* The change introduced with 9.1.10 created another problem that might
lead to premature request completion (kernel crash); reverted that
change and fix it in another way
* 9.1.10 (api:genl2/proto:86-121/transport:18)
* fix a regression introduced with 9.1.9; using protocol A on SMP
with heavy IO can might cause kernel crash
* 9.1.9 (api:genl2/proto:86-121/transport:18)
* fix a mistake in the compat generation code; it broke DRBD on
partitions on kernel older than linux 5.10 (this was introduced
with drbd-9.1.8; not affected: logical volumes)
* fix for a bug (introduced with drbd-9.0.0), that caused possible
inconsistencies in the mirror when using the 'resync-after' option
* fix a bug that could cause a request to get stuck after an unlucky
timing with a loss of connection
* close a very small timing window between connect and promote that
could lead to the new-current-uuid not being transmitted to the
concurrently connecting peer, which might lead to denied connections
later on
* fix a recently introduced OOPS when adding new volumes to a
connected resource
* fix online attach when the connection to a 3rd node is down
* 9.1.8 (api:genl2/proto:86-121/transport:18)
* restore protocol compatibility with drbd-8.4
* detect peers that died silently when starting a two-phase-commit
* correctly abort two-phase-commits when a connection breaks between
phases 1 and 2
* allow re-connect to a node that was forced into secondary role and
where an opener is still present from the last time it was primary
* fix a race condition that allowed to configure two peers with the
same node id
* ensure that an open() call fails within the auto-promote timeout
if it can not succeed
* build fixes for RHEL9
* following upstream changes to DRBD up to Linux 5.17 and updated compat
* 9.1.7 (api:genl2/proto:110-121/transport:18)
* avoid deadlock upon trying to down an io-frozen DRBD device that
has a file system mounted
* fix DRBD to not send too large resync requests at multiples of 8TiB
* fix for a "forgotten" resync after IO was suspended due to lack of quorum
* refactored IO suspend/resume fixing several bugs; the worst one could
lead to premature request completion
* disable discards on diskless if diskful peers do not support it
* make demote to secondary a two-phase state transition; that guarantees that
after demotion, DRBD will not write to any meta-data in the cluster
* enable "--force primary" in for no-quorum situations
* allow graceful recovery of primary lacking quorum and therefore
have forzen IO requests; that includes "--force secondary"
* following upstream changes to DRBD up to Linux 5.15 and updated compat
* 9.1.6 (api:genl2/proto:110-121/transport:17)
* fix IO to internal meta-data for backing device larger than 128TB
* fix resending requests towards diskless peers, this is relevant when
fencing is enabled, but the connection is re-established before fencing
succeeds; when the bug triggered it lead to "stuck" requests
* remove lockless buffer pages handling; it still contained very hard to
trigger bugs
* make sure DRBD's resync does not cause unnecessary allocation in
a thinly provisioned backing device on a resync target node
* avoid unnecessary resync (or split-brain) due to a wrongly generated
new current UUID when an already IO frozen DBRD gets new writes
* small fix to autopromote, when an application tries a read-only open
before it does a read-write open immediately after the peer primary
vanished ungracefully
* split out the secure boot key into a package on its own, that is
necessary to allow installation of multiple drbd kernel module packages
* Support for building containers for flacar linux
* 9.1.5 (api:genl2/proto:110-121/transport:17)
* merged all changes from drbd-9.0.32
- fix a read-access-after-free, that could cause an OOPs; triggers with
an unusual configuration with a secondary having a smaller AL than
the primary or a diskless primary and heavy IO
- avoid a livelock that can cause long IO delays during resync on a
primary resync-target node
- following upstream changes to DRBD up to Linux 5.14 and updated compat
(including RHEL9-beta)
- fix module override for Oracle-Linux
* fixed a locking regression of the 9.1 branch, only relevant in
the moment a local backing device delivers an IO error to drbd
* removed compat support for kernel older than Linux-3.10 (RHEL7)
* code cleanups and refactoring
* 9.1.4 (api:genl2/proto:110-121/transport:17)
* merged all changes from drbd-9.0.31
* enabled dynamic debug on some additional log messages
* remove (broken) write conflict resolution, replace it with warning
about the fact
* debugfs entry for the interval tree
* 9.1.3 (api:genl2/proto:110-120/transport:17)
* merged all fixes from drbd-9.0.30-0rc1
* fix a corner-case NULL deref in the lockless buffer pages handling; the
regression was introduced with 9.1.0 (released Feb 2021); To my knowledge
it took 6 months until someone triggered it for the first time
* fix sending a P_PEERS_IN_SYNC packet into a fresh connection (before
handshake packets); this problem was introduced when the drbd-8.x
compatibility code was removed
* remove sending a DRBD-barrier packet when processing a REQ_PREFLUSH
request, that improves IO-depth and improves performance with that
* 9.1.2 (api:genl2/proto:110-120/transport:17)
* merged all fixes from drbd-9.0.29; other than that no changes in this branch
* 9.1.1 (api:genl2/proto:110-119/transport:17)
* fix a temporal deadlock you could trigger when you exercise promotion races
and mix some read-only openers into the test case
* fix for bitmap-copy operation in a very specific and unlikely case where
two nodes do a bitmap-based resync due to disk-states
* fix size negotiation when combining nodes of different CPU architectures
that have different page sizes
* fix a very rare race where DRBD reported wrong magic in a header
packet right after reconnecting
* fix a case where DRBD ends up reporting unrelated data; it affected
thinly allocated resources with a diskless node in a recreate from day0
event
* changes to socket buffer sizes get applied to established connections immediately;
before it was applied after a re-connect
* add exists events for path objects
* fix a merge-mistake that broke compatibility with 5.10 kernels
* 9.1.0 (api:genl2/proto:110-119/transport:16)
* was forked off from drbd 9.0.19
* has all changes up to 9.0.28-1
* locking in the IO-submit code path was considerably improved,
allowing multiple CPU to submit in parallel
* rename patch
- fix-resync-finished-with-syncs-have-bits-set.patch
+ bsc-1025089_fix-resync-finished-with-syncs-have-bits-set.patch
* remove patches which are already included in upstream code:
- bsc-1192929_01-make_block_holder_optional.patch
- bsc-1192929_02-move_kvmalloc_related_to_slab.patch
- bsc-1192929_03-polling_to_bio_base.patch
- bsc-1192929_04-pass_gend_to_blk_queue_update_readahead.patch
- bsc-1192929_07-add_disk_error_handle.patch
- bsc-1192929_08-have_void_drbd_submit_bio.patch
- bsc-1192929_09-remove_bdgrab.patch
- bsc-1201335_01-compat-test-and-cocci-patch-for-bdi-in-gendisk.patch
- bsc-1201335_02-compat-only-apply-bdi-pointer-patch-if-bdi-is-in-req.patch
- bsc-1201335_03-genhd.patch
- bsc-1201335_04-bio_alloc_bioset.patch
- bsc-1201335_05-bio_alloc.patch
- bsc-1201335_06-bdi.patch
- bsc-1201335_07-write-same.patch
- bsc-1201335_08-bio_clone_fast.patch
- bsc-1202600_01-remove-QUEUE_FLAG_DISCARD.patch
- bsc-1202600_03-block-decouple-REQ_OP_SECURE_ERASE-from-REQ_OP_DISCA.patch
- bsc-1202600_04-remove-assign_p_sizes_qlim.patch
- bsc-1206791-01-drbd-add-comments-explaining-removal-of-bdi-congesti.patch
- bsc-1206791-02-drbd-fix-static-analysis-warnings.patch
* Fri Jan 06 2023 [email protected]
- drbd: add patches to follow upstream code style and remove build warning (bsc#1206917)
* update bsc-1201335_06-bdi.patch commit log (no code change)
+ bsc-1201335_06-bdi.patch
* add new patches
+ bsc-1206791-01-drbd-add-comments-explaining-removal-of-bdi-congesti.patch
+ bsc-1206791-02-drbd-fix-static-analysis-warnings.patch
* Sat Dec 03 2022 [email protected]
- update to 9.0.30 from commit 10bee2d5 to 8e9c0812
* drbd failed to build for x86_64 with new kernel (bsc#1205254)
- remove files:
drbd-9.0.30~1+git.10bee2d5.tar.bz2
compat_genl_maxattr_in_ops.patch
convert_to_blk_alloc_disk.patch
drbd-Fix-abortion-of-a-connect-2-phase-commit.patch
- add files:
drbd-9.0.30~1+git.8e9c0812.tar.bz2
bsc-1192929_02-move_kvmalloc_related_to_slab.patch
bsc-1192929_03-polling_to_bio_base.patch
bsc-1192929_07-add_disk_error_handle.patch
bsc-1192929_08-have_void_drbd_submit_bio.patch
bsc-1201335_03-genhd.patch
bsc-1201335_04-bio_alloc_bioset.patch
bsc-1201335_05-bio_alloc.patch
bsc-1201335_07-write-same.patch
bsc-1201335_08-bio_clone_fast.patch
bsc-1202600_01-remove-QUEUE_FLAG_DISCARD.patch
bsc-1202600_03-block-decouple-REQ_OP_SECURE_ERASE-from-REQ_OP_DISCA.patch
bsc-1202600_04-remove-assign_p_sizes_qlim.patch
* Fri Nov 18 2022 [email protected]
- drbd failed to build for x86_64 with new kernel (bsc#1205254)
+ bsc-1192929_01-make_block_holder_optional.patch
+ bsc-1192929_04-pass_gend_to_blk_queue_update_readahead.patch
+ bsc-1192929_09-remove_bdgrab.patch
+ bsc-1201335_01-compat-test-and-cocci-patch-for-bdi-in-gendisk.patch
+ bsc-1201335_02-compat-only-apply-bdi-pointer-patch-if-bdi-is-in-req.patch
+ bsc-1201335_06-bdi.patch
* Mon Sep 13 2021 [email protected]
- bsc#1190359, update to 9.0.30
* fix a crash when drbd-9 node gets connected to a drbd-8.4 node, the
regression was introduced between 9.0.25 and 9.0.26
* A improved approach to serialize rsyncs from multiple sources; the previous
one could cause wrong accounting for online verify
* fix a race condition that could cause resync operations to stall when the
completion of one resync allows another one to proceed
* fix a race condition that could cause an online verify operation to not
terminate under specific conditions (corking enabled no other IO)
* fix locking of drbd_devices idr that caused (very rarely) create/remove
minor to fail
- Add patch convert_to_blk_alloc_disk.patch (kernel b647ad024)
- Remove patch Revert-drbd-serialize-syncs-from-multiple-sources.patch
Remove patch drbd-fix-race-condition-resetting-resync_next_bit.patch
Remove patch drbd-Fix-a-possible-NULL-deref-found-with-gcc-11-fan.patch
Remove patch drbd-change-to-L_VERIFY_S-after-peer-is-L_VERIFY_T.patch
Remove patch drbd-fix-termination-of-verify-with-stop-sector.patch
Remove patch drbd-remove-device_to_minor.patch
Remove patch drbd-use-DEFINE_MUTEX-insteadm-of-mutex_init.patch
Remove patch drbd-Fix-locking-for-the-drbd_devices-idr.patch
Remove patch drbd-fix-protocol-compatibility-with-drbd-8.4-state.patch
- Disable rt build for x86_64 temporarily due to not kernel-rt still in 5.3.18
* Fri May 07 2021 [email protected]
- bsc#1188472, update to 9.0.29
* fix data corruption when DRBD's backing disk is a degraded Linux software
raid (MD)
* add correct thawing of IO requests after IO was frozen due to loss of quorum
* fix timeout detection after idle periods and for configs with ko-count
when a disk on an a secondary stops delivering IO-completion events
* fixed an issue where UUIDs where not shifted in the history slots; that
caused false "unrelated data" events
* fix switching resync sources by letting resync requests drain before
issuing resync requests to the new source; before the fix, it could happen
that the resync does not terminate since a late reply from the previous
caused a out-of-sync bit set after the "scan point"
* fix a temporal deadlock you could trigger when you exercise promotion races
and mix some read-only openers into the test case
* fix for bitmap-copy operation in a very specific and unlikely case where
two nodes do a bitmap-based resync due to disk-states
* fix size negotiation when combining nodes of different CPU architectures
that have different page sizes
* fix a very rare race where DRBD reported wrong magic in a header
packet right after reconnecting
* fix a case where DRBD ends up reporting unrelated data; it affected
thinly allocated resources with a diskless node in a recreate from day0
event
* speedup open() of drbd devices if promote has not chance to go through
* new option "--reset-bitmap=no" for the invalidate and invalidate-remote
commands; this allows to do a resync after online verify found differences
* changes to socket buffer sizes get applied to established connections
immediately; before it was applied after a re-connect
* add exists events for path objects
* forbid keyed hash algorithms for online verify, csyms and HMAC base alg
* fix a regression introduces with 9.0.25; it failed to determine the
right device size and the connection hangs in WFBitmapS/WFBitmapT
repl state; to trigger this you need to do a partial resync to a
new node with different backing device size
* fix an issue with netlink packets processed in parallel on multiple
CPUs; the bug caused drbdadm adjust failing in very rare cases
* fix a very rare occurrence of a reconciliation resync getting stuck
* fix a race condition that causes a detach operation to hang; it
is very hard to trigger
* fix a kernel OOPS (via a BUG()) upon adding a timer twice under very rare
timing
* fix a counter imbalance that could lead to assertion messages when a
protocol A peer disconnects with a certain timing
* fix a rare race with receiving bitmap and a state change while
establishing a connection
* fix UUID handling to avoid false split-brain detections; this bug got
triggered an isolated primary that gets demoted, and temporal network
interruptions among the remaining nodes
* fix resync decision to obey disk states when the generation UUIDs are
equal; the effect of this bug was that you could end up with two Outdated
nodes after resync
* fix concurrent disk-attach operations
* Fix possible kernel warning regarding an inbalance of backing device
link/unlink
* move some amount of kernel backward compatibility code moved from the old
method (drbd_wrappers.h) to new cocci semantic patches
* add support renaming resources while its devices might be in use and
process IO requests
* Allow setting c_max_rate to 0 with the meaning that the resync controller
has no upper limit for the resync speed
* Fix regression: allow live migration between two diskful peers again
* following upstream changes to DRBD up to Linux 5.12 and updated compat
rules to support up to Linux 5.12
- Remove patch compat_blk_queue_stack_limits.patch
Remove patch compat_get_fs.patch
Remove patch compat_remove_kernel_setsockopt.patch
Remove patch compat-test-header.patch
Remove patch drbd-fix-zero-metadata-limit-by-page-size-misaligned.patch
Remove patch remove_bdi_cap_stable_writes.patch
Remove patch submit-bio-private-date.patch
- Modify patch suse-coccinelle.patch
- Add patch compat_genl_maxattr_in_ops.patch (48526a0f)
- Bug fixes between 9.0.29 and 9.0.30
Add patch drbd-change-to-L_VERIFY_S-after-peer-is-L_VERIFY_T.patch
Add patch drbd-Fix-abortion-of-a-connect-2-phase-commit.patch
Add patch drbd-Fix-a-possible-NULL-deref-found-with-gcc-11-fan.patch
Add patch drbd-Fix-locking-for-the-drbd_devices-idr.patch
Add patch drbd-fix-protocol-compatibility-with-drbd-8.4-state.patch
Add patch drbd-fix-race-condition-resetting-resync_next_bit.patch
Add patch drbd-fix-termination-of-verify-with-stop-sector.patch
Add patch drbd-remove-device_to_minor.patch
Add patch drbd-use-DEFINE_MUTEX-insteadm-of-mutex_init.patch
Add patch Revert-drbd-serialize-syncs-from-multiple-sources.patch
- cocci apply: linux-5.12.0-2
queue_discard_zeroes_data__no_present (48920ff2a5a9)
* Wed Dec 09 2020 [email protected]
- bsc#1179708, compat to kernel v5.10
- Add patch compat_get_fs.patch
Add patch remove_bdi_cap_stable_writes.patch
* Tue Dec 08 2020 [email protected]
- Update to 9.0.26
* fix a case of a disk unexpectedly becoming Outdated by moving the
exchange of the initial packets into the body of the two-phase-commit
that happens at a connect
* fix adding of new volumes to resources with a primary node
* reliably detect split brain situation on both nodes
* fix an unexpected occurrence of NetworkFailure state in a tight
drbdsetup disconnect; drbdsetup connect sequence
* fix online verify to return to Established from VerifyS if the VerifyT node
was temporarily Inconsistent during the run
* fix a corner case where a node ends up Outdated after the crash and rejoin
of a primary node
* implement 'blockdev --setro' in DRBD
* following upstream changes to DRBD up to Linux 5.9 and ensure
compatibility with Linux 5.8 and 5.9
* fix a crash if during resync a discard operation fails on the
resync-target node
* fix online verify to not clamp disk states to UpToDate
* fix promoting resync-target nodes; the problem was that it could modify
the bitmap of an ongoing resync; which leads to alarming log messages
* pause a resync if the sync-source node becomes inconsistent; an example
is a cascading resync where the upstream resync aborts and leaves the
sync-source node for the downstream resync with an inconsistent disk;
note, the node at the end of the chain could still have an outdated disk
(better than inconsistent)
* allow force primary on a sync-target node by breaking the resync
* minor fixes to the compat tests
* fix for writes not getting mirrored over a connection while the primary
transitions through the WFBitMapS state
* completed missing logic of the new two-phase-commit based connect process;
avoid connecting partitions with a primary in each; ensure consistent
decisions if the connect attempt will be retried
- Add patch compat-test-header.patch
Add patch submit-bio-private-date.patch
Add patch compat_remove_kernel_setsockopt.patch
Add patch compat_blk_queue_stack_limits.patch
- Remove patch rely-on-sb-handlers.patch (187bddac0)
Remove patch fix-err-of-wrong-return-type.patch (969310232)
Remove patch compat_generic_make_request.patch (8615d6837)
Remove patch blk_alloc_queue_make_request.patch (edaa9b0f/fb59b40e)
Remove patch remove_congested_fn_congested_data.patch (34484003/9b80d46b)
* Tue Nov 03 2020 [email protected]
- bsc#1178388, build error with -Wreturn-type
Add patch fix-err-of-wrong-return-type.patch
* Sat Oct 10 2020 [email protected]
- bsc#1177417, kernel oops when submit bio
Modify patch compat_generic_make_request.patch
Modify patch blk_alloc_queue_make_request.patch
- jsc#11801, remove is_opensuse macro for SLE15SP3 only,
tumbleweed not support RT yet.
* Thu Sep 17 2020 [email protected]
- update to 9.0.25-0rc1
* fix a race condition between receiving UUIDs and finishing a resync
that can lead to a false-positive split-brain detection later on
* fix access after free of peer_req objects, that only happened when
a resync target node is paused sync source at the same time
* fix abortion of local state changes in case they can not proceed due
to loss of connection
* fix corner cases with reconciliation resync and parallel promote
* fix an issue establishing a connection when the multipath feature is
used to connect to a stacked resource without a dedicated service IP
* fix sometimes a peer-disk state to another resync-target staying Outdated
after two resyncs from the same sync source node finish
* fix an (unlikely) deadlock while establishing a connection
* deactivate the kref_debug code, it has performance implicatios
* Introduce the "disconnected" hander; it receives the last connection
state in the evnironment variable DRBD_CSTATE
- Changes of drbd-9.0.24-1
* fix deadlock when connecting drbd-9 to drbd-8.4 and the drbd-9
side becomes sync-source
* fix an issue with 3 (or more) node configurations; with a diskless node
and two storage nodes; if one of the storage nodes was hard rebooted
and came back and the diskless got primary and did not issue write
requests and the returning storage node established a connection with
the surviving storage node first, DRBD failed to upgrade the disk
state to UpToDate after the resync
* detect split-brain situations also when both nodes are primary;
this is how it was in drbd-8.4; up to now drbd-9 did not realize
the split-brain since it complains about the not allowed dual
primary first; for this change a new protocol version was necessary
* verified it compiles with Linux 5.7
- bsc#1176749, add compatible patches to SLE15 SP3 kernel.
block layer api backport from kernel v5.9
Add patch blk_alloc_queue_make_request.patch
Add patch compat_generic_make_request.patch
Add patch remove_congested_fn_congested_data.patch
* Wed Jun 10 2020 [email protected]
- bsc#1172761, Update to drbd-9.0.23-1
* fix a deadlock (regression introduced in 9.0.22) that can happen when
new current UUID is generated while a connection gets established
* Do not create a new data generation if the node has
'allow-remote-read = no' set, is primary, and the local disk fails
(because it has no access to good data anyome)
* fix a deadlock (regression introduced in 9.0.22) that can be
triggered if a minor is added into a resource with an established
connection
* generate new UUID immediately if a primary loses a disk due to an IO
error
* fix read requests on diskless nodes that hit a read error on a
diskful node; the retry on another diskful node works, but a bug
could lead to a log-storm on the diskless node
* fix removal of diskless nodes from clusters with quorum enabled
(initiated from the diskless itself)
* fix wrongly declined state changes if connections are established
concurrently
* fix continuation of initial resync; before that the initial resync
always started from the beginning if it was interrupted
* use rwsem _non_owner() operations to avoid false positives of
lock-dep when running on a debug kernel
* fix a sometimes missed resync if only a diskless node was primary
since the day0 UUID
* fix a corner case where a SyncSource node does not recognise
that a SyncTarget node declared the resync as finished
* update compat up to Linux 5.6
- Remove patch without_pr_warning.patch since change in 7e6a20f7
* Wed Jun 10 2020 [email protected]
- jsc#11801, enable buildrt for Leap15.2 but Tumbleweed.
* Tue Mar 10 2020 [email protected]
- bsc#1166298, Update to drbd-9.0.22-1
* introduce locking to avoid connection retries when UUIDs or
relevant flags change during the exchange of this data
* improve serialization of events after loosing a primary
* fix a constraint in sanitize state that can caused a promote to be
deliced by some other node
* fix a case of a false positive detection of a split brain condition
* allow a resync target to switch to the resync source with less
bits out of sync
* fix bitmap UUID after resync to use current UUID from self rather
than sync source
* fix pushing bitmap UUID into history when changed
* fix regression introduced with 9.0.20, that can cause a missed
resync after a reconciliation resync
* fix regression introduced with 9.0.20, that can cause a missed
resync after a promote on a diskless node
* fix UUID handling in case a node promotes during (a short)
reconciliation resync
* fix removing of a diskless node when quorum is enabled
* Tue Feb 25 2020 [email protected]
- Update to drbd-9.0.21-1, require coccinelle >= 1.0.8
* fix compat for write same on linux 4.9 and the Debian users
* fix kernel compat for linux 4.8 and 4.9; this mainly affected Debian
users; The symptoms where slow resync and resync getting stuck always at
the same point
* enable resync of lost and re-created backing devices (think lost node) when
the backing device was thinly provisioned and its current uuid is pre-set
to a 'day0 UUID' (by LINSTOR); that works by copying a unused bitmap slot
which tracks all changes since day 0
* fix attach when bitmap is on PMEM; before it was set to
'all blocks out-of-sync' upon attach
* avoid doing reconciliation resync multiple times by updating the
resync target's dagtag after if completed successfully
* return disk-state from Outdated to UpToDate when it loses connection
while in WFBitMapT and we have a stable and UpToDate peer
* new option --force-resync flag can be passed to new-current-uuid, that
can be used to trigger initial resync without touching the role
- Remove upstream drbd-update-resync-target-s-dagtag.patch
- Modify patch suse-coccinelle.patch to adopt spaas
* Fri Jan 03 2020 [email protected]
- bsc#1159786, fix build issue against v5.5
add patch without_pr_warning.patch
* Thu Dec 26 2019 [email protected]
- bsc#1159333, back port patch for duplicate resync.
add patch drbd-update-resync-target-s-dagtag.patch
* Mon Dec 16 2019 [email protected]
- bsc#1158446, fix metadata limit due to 64k page size of ppc64le.
add patch drbd-fix-zero-metadata-limit-by-page-size-misaligned.patch
* Thu Oct 17 2019 [email protected]
- Remove obsolete Groups tag (fate#326485)
* Fri Oct 11 2019 [email protected]
- Update to drbd-9.0.20-1
* fix a case of false split brain detection if a diskless node promotes
multiple times, by aligning the rules for generating a new current-UUID
on a diskless nodes with them on a node with disk
* check if we still have quorum by exchanging a drbd-ping with peers
before creating new current UUID after loosing one peer
* fix after weak handling to not interfere with reconciliation resyncs
* retry connect when one of the relevant flags changes during UUID exchange
* fix reconciliation resync if one of the secondary got an current-UUID update
* fix resync to make progress after it was paused by an other resync operation
* fix false split-brains when a resync source changes current-UUID during
resync operation
* fix restore of D_OUTDATED when the resource first only attached and
then the peer objects are created (in contrast to the usual, new-peer,
attach, connect)
* abort creating new current-UUID when writing to meta-data fails in
the moment where the new-current-UUID should be written
* removed DRBD marking itself as read-only when secondary; this flag
was exposed using the BLKROGET ioctl; that should be left to user-land
use; recent KVM checks that flag, and does not dare auto-promote when
set by DRBD
* fix a small memory-leak when creating peer devices
* fix a possible information leak of kernel memory that pads net-link packets
* completing implications of "allow-remote-read=no"; i.e. when not to
create a new-current-UUID as read-write access to the data set was lost;
also fail both reads and writes if reads are no longer possible
* new option value "rr-conflict=retry-connect"; that helps in scenarios with
quorum where stopping a service takes longer than a temporarily network
outage and DRBD's reconnect
* code cleanups, introduced enums for remaining magic numbers
* new kernel-backward-compatibility framework based on spatch/coccinelle,
replacing an unmaintainable moloch of C preprocessor hell; Merged the
complete kernel-compat submodule
* ships with pre-computed compat-patches for main distros' kernels; in case
an other kernel is found it tries to use local spatch, if that is not
installed the build process tries to use a LINBIT hosted web service
to create the compat patch ("spatch-as-a-service").
* compat with up to Linux-5.3-rc2
- Modify patch suse-coccinelle.patch to adopt spaas
* Fri Sep 20 2019 [email protected]
- bsc#1151579, fix collinelle default path and always trigger in obs
Add patch suse-coccinelle.patch
* Tue Sep 17 2019 [email protected]
- bsc#1146117, disallow dual primaries when not configured.
Modify patch rely-on-sb-handles.patch
* Tue Sep 10 2019 [email protected]
- Restore higher summary specifity.
- Drop old-age %clean, %defattr.
* Mon Sep 09 2019 [email protected]
- bsc#1149945, update to 8e93a5d93 (drbd-9.0 branch)
* Coccinelle support
* compat with up to Linux-5.3
- Remove patch compat_no_bioset_initialized.patch
* Fri Jul 19 2019 [email protected]
- Update to 9.0.19-1
* check on CAP_SYS_ADMIN instead of CAP_NET_ADMIN for certain operations
* fix detection of unstable resync
* fix possible stuck resync when resync started from an other secondary
and later continued from a primary
* fix NULL dereference with disk-timeout enabled; was introduced in 9.0.9
* retry connect when own current UUID changes during UUID exchange
* fix quorum tie-breaker diskless logic for settings other than "majority"
* disable quorum tie-breaker for 0 voters
* fix dax_direct_access() error return check
* fix resync stuck at near completion; bug was intorduces with 9.0.17
* unblock IO when on-quorum-lost policy is changed (suspend -> io-error)
* introduce allow-remote-read configuration option; set it to "no" for
DR links you only want to write, but never read
* only complain about UUID changes during initial handshake
* Tue May 28 2019 [email protected]
- Upgrade to 9.0.18-1
* Fix an IO deadlock under memory pressure
* Fix disconnect timing in case the network connection suddenly
drops all packets
* Fix some misbehavior that surfaced with Ahead/Behind
* Fix potential spinlock deadlock in IRQ
* Minor fixes: forget-peer, _rcu iterators
* Quickly stop resync during AHEAD/BEHIND by introducing new
packet for that purpose.
* The quorum feature can now use the connectivity to
the majority of Diskless nodes as tiebreaker
* Access meta-data using DAX if it is on persistent memory
(NVDIMM or PMEM); For write intense workloads this is a x2 to x4 speedup!
- Remove patch fix-make-error.patch since merged into upstream(46e8e3fc)
* Fri Mar 22 2019 [email protected]
- Upgrade to 9.0.17-1
* Fix UUID handling of a diskless primary that has not peer with
usable data may not touch the current UUID
* Fix resync-after dependencies; cross-resource dependencies
and missing resources
* Fix resync when the sync source suddenly connects to a more recent
data set via an other connection and becomes sync target on that
other connection; pause first resync; fix wrong display of negative
resync progress percentage in this case
* Fix volume numbers between 32767 and 65534
* Fix the data integrity implementation; it was broken since drbd-9.0
and reported only false positives
* Fix for a corner-case when a promote action happens concurrently with
a reconciliation resync
* Improve resync code to be able to fully utilize fast storage
backend devices and fast networks with resync traffic; as a side
effect the settling time of the resync controller got shorter in
for most cases
* Show in the user-visible message who the opener is if if demote/down
fails doe to someone holding a drbd device open
* docker file for a "load drbd module container" and allow to disable
user-mode-helpers, which is necessary for this container
- Add patch fix-make-error.patch for build error of make against TW.
* Thu Jan 10 2019 [email protected]
- bsc#1118732, split brain handles malfunction when 2 primaries.
- Add patch rely-on-sb-handlers.patch
* Mon Dec 10 2018 [email protected]
- bsc#1118841, kernel compatible issue.
Have bioset_init but no bioset_initialized
- Add patch compat_no_bioset_initialized.patch
Remove patch compat_have_mempool_init.patch
* Wed Nov 21 2018 [email protected]
- bsc#1116820, kernel compatible issue of sle15sp1
- Add patch compat_have_mempool_init.patch
* Fri Oct 26 2018 [email protected]
- bsc#1115606, Update to 9.0.16-1
* Fix regression (introduced with 9.0.15) in handling request timeouts
* Fix a possible distributed loop when establishing a connection
* Fix a corner case in case a resync "overtakes" an other one
* Fix clearing of the PRIMARY_LOST_QUORUM flag
* Check peers before generating new current UUID after loosing a node
* In case the locally configured address of a connection is not
available keep on retrying until it comes back
* Mon Jul 23 2018 [email protected]
- Update to 9.0.15-1
* fix tracking of changes (on a secondary) against the lost disk of a
primary and also fix re-attaching in case the disk is replaced
* fix live migrate of VMs on DRBD when migrated to/from diskless nodes
* fix an IO deadlock in DRBD when the activity log on a secondary runs
full
* fix hanging demote after IO error followed by attaching the disk
again and the corresponding resync
* fix DRBD dopping connection after an IO error on the secondary node
* improve details when online changing devices from diskless to with
disk and vice versa. (Including peers freeing bitmap slots)
* new module parameter to disable support for older protocol versions
* improve details when online changing devices from diskless to with disk
* remove no longer relevant compat tests
* expose openers via debugfs
* optimize IO submit code path
* compat for v4.18 kernel
* Thu May 03 2018 [email protected]
- Update to 9.0.14-1
* fix regression in 9.0.13: call after-split-brain-recovery
handlers no auto-recovery strategies (not even the default:
disconnect) would be applied, nodes would stay connected
and all nodes would try to become the source of the resync.
* fix spurious temporary promotion failure: if after Primary
loss failover happened too quickly, transparently retry internally.
* fixup recently introduced P_ZEROES to actually work as intended
* fix online-verify to account for skipped blocks; otherwise,
it won't notice that it has finished, apparently being stuck
near "100% done"
* expose more resync and online-verify statistics and details
* improve accounting of "in-flight" data and resync requests
* allow taking down an already useless minor device during "down",
even if it is (temporarily) opened by for example udev scanning
* fix for a node staying "only" Consistent and not returning
to UpToDate in certain scenarios when fencing is enabled
* fix data generation UUID propagate during resync
* compat for upstream kernels up to v4.17
* Sun Apr 08 2018 [email protected]
- bsc#1090167, Update to 9.0.13-1
* abort a resync if a resync source becomes weakly and the sync
targetis a neighbor of the primary
* fix UUID handling with multiple diskless nodes
* When a data-set gets into contact with an all diskless cluster,
make sure to either set it to "Consistent" or reject the attach
* correctly handle when a node that was marked as intentional
diskless should get a disk
* fix outdating of weakly connected nodes
* made returning from Ahead to SyncSource more reliable
* fix a hard to trigger deadlock in the receiver
* fix online resize in the presence of two or more diskless nodes
* fix online add of volumes to diskless nodes when it already has
established connections
* Set the SO_KEEPALIVE socket option on data sockets
* automatically solve a specific split brain when quorum is enabled
* Compat: Added support for kernels up to v4.15.x
* new wire packet P_ZEROES a cousin of P_DISCARD, following the
kernel as it introduced separated BIO ops for writing zeros
and discarding
* compat workaround for two RHEL 7.5 idiosyncrasies regarding
refcount_t and struct nla_policy
- Remove patch support-timer-setup.patch. Upstream fix 74b1cbb274
* Sun Feb 11 2018 [email protected]
- bsc#1080458, enable build with kernel-rt on x86_64.
- bsc#1080459, support build against 4.15.0.
setup_timer() change to timer_setup()
- Add patch support-timer-setup.patch
* Wed Jan 24 2018 [email protected]
- bsc#1077318, Update to 9.0.12
* Fix a race condition in the device_open code path that can cause an
internal counter to go negative
- Update to 9.0.11
* Fix bug in compat code: Without this fix large bios are not split.
* Wed Dec 06 2017 [email protected]
- bsc#1074169, Update to 9.0.10-1
* Fix resync of two secondary nodes in the presence of
a 3rd node that is primary (maybe with disk or diskless);
Fixed the race condition that caused the resync to sometimes not terminate
* Improve connection behavior with autopromote enable one node Primary and
udev present.
* Fix in memory alignment of DRBD's struct bio.
* Improve the quorum implementation, so that is works nicely with for the
purpose of replacing fencing with quorum in a Pacemaker setup.
* Ensure compatibility with upstream Linux kernel 4.14
- Remove patch reproducible.patch
* Fri Nov 17 2017 [email protected]
- bsc#1068587, add build request libelf-devel to build.
* Wed Oct 11 2017 [email protected]
- bsc#1062749, disable buildrt against SLE15 x86_64 temporarily.
This change will be removed when rt is ready.
* Fri Oct 06 2017 [email protected]
- bsc#1061981, update to 9.0.9
* fix occasionally forgotten resyncs in installations where
diskless primaries are present.
* fix an issue that causes unexpected split-brain upon connect.
* in a cluster with a diskless primary, when a server goes away,
and is not outdated, outdate it upon reconnect.
* fix update of exposed data UUID on diskless primaries.
* fix a possible OOPS when in a debug message regarding bitmap
locking
* fix discard bigger than 1MiB
* fix left over bits in bitmap on SyncSource after resync
* fix peers becoming unexpectedly displayed as D_OUTDATED at the
end of a resync
* fix a race between auto promote and auto demote of multiple volumes
in a single resource
* Speed up down of many resources by using call_rcu() instead
of synchronize_rcu()
* Make it compatible with the soon to be released 4.13 kernel
- Modify reproducible.patch since part of the patch is merged
* Wed Jul 19 2017 [email protected]
- Add reproducible.patch to sort file lists (boo#1041090)
and to override build date (boo#1047218) to fix build-compare
* Wed Jun 14 2017 [email protected]
- bsc#1045473, update to 9.0.8
fix a race condition between adding connections and receiving data
fix a OOPS on a diskfull node when a request from a diskless node
fix a distributed deadlock when doing a discard/write-same burst
fix an issue with diskless nodes adopting wrong current UUIDs
fix wrongly rejected two-phase-state transactions
fix initial resync, triggered by "--force primary"(regression 9.0.7)
Speed-up AL-updates with bio flags REQ_META and REQ_PRIO
Merged changes from 8.4.10 and with that compatibility with Linux-4.12
- Remove patch fix-initial-sync-stop.patch
- Fix the license to GPL-2.0+
* Thu May 25 2017 [email protected]
- bsc#1038852, fix initial sync not triggered
add patch fix-initial-sync-stop.patch
* Wed Apr 26 2017 [email protected]
- Update to 9.0.7
Using 9.0.7rc2 for upgrading from rc1...
- bsc#1028124, fix kernel compat
- Fix a potenial split brain
- Change the drbd-utils requirement to 8.9.11
* Fri Mar 24 2017 [email protected]
- Update to 9.0.7rc1
- various fixes to the 2-phase-commit online resize
fix fencing and disk state trasition and from consistent, necessary
for crm-fence-peer
fix calculation of authoritative nodes
Quorum to avoid data divergence, an alternative to fencing
Compat with Linux 4.10
- Remove patch drbd_wrapper-Blank-out-WRITE_SYNC-warning-for-new-ke.patch
- Add fix-resync-finished-with-syncs-have-bits-set.patch for bsc#1025089
- Including the compatible fix of bsc#1031299
* Mon Mar 06 2017 [email protected]
- Compability fixes for SLE12 SP3 (bsc#993388, FATE#321732)
- Add patch drbd_wrapper-Blank-out-WRITE_SYNC-warning-for-new-ke.patch
* Thu Feb 16 2017 [email protected]
- bsc#1025585, upgrade to 9.0.6
* Fri Nov 25 2016 [email protected]
- Excluded openSUSE from RT KMP build (bsc#1005578)
* Sat Nov 19 2016 [email protected]
- Enabled RT KMP build (bsc#1005578)
* Mon Oct 24 2016 [email protected]
- bsc#1006176, compat with kernel 4.8 with 9.0.5
* Mon Oct 24 2016 [email protected]
- Upgrade 9.0.2 to 9.0.5
- Remove patch compat-4.7-9902af79-i_mutex.patch
Remove patch compat-4.7-fe8fb75e-blk_queue_write_cache.patch
Remove patch compat-4.7-50225243-kill-nla_put_u64.patch
Remove patch compat-4.7-1dee3f59-align-nla-u64.patch
Remove patch drbd-buildcompare.patch
Remove patch kernel-4.5-compat.patch
Remove patch temp.patch
* Wed Jun 08 2016 [email protected]
- bsc#983633, upgrade to ver9.0.2 to build against kernel 4.6/4.7
- Add patch compat-4.7-9902af79-i_mutex.patch
- Add patch compat-4.7-fe8fb75e-blk_queue_write_cache.patch
- Add patch compat-4.7-50225243-kill-nla_put_u64.patch
- Add patch compat-4.7-1dee3f59-align-nla-u64.patch
* Fri Apr 08 2016 [email protected]
- Compat with kernel 4.5
- Add patch kernel-4.5-compat.patch
* Mon Mar 07 2016 [email protected]
- Remove timstamp from binaries
Add patch drbd-buildcompare.patch
* Mon Mar 07 2016 [email protected]
- Update to release drbd-9.0.1
- Depend on drbd-utils >= 8.9.6
* Mon Nov 30 2015 [email protected]
- Update to released drbd-9.0.0
- Remove patch 0001-Support-zeroout-device-in-initial-sync.patch
- Remove patch update-to-8.4.6-5.patch
- Remove patch rename-GFP_WAIT-to-GFP_RECLAIM.patch
- Remove patch new-bio-struct.patch
* Fri Nov 20 2015 [email protected]
- BSC#955968, support GFP_RECLAIM in kernel4.4
- Add rename-GFP_WAIT-to-GFP_RECLAIM.patch
* Thu Oct 22 2015 [email protected]
- BSC#950477, support new bio struct in kernel4.3
- Add new-bio-struct.patch
* Fri Oct 16 2015 [email protected]
- BSC#950477, update to 8.4.6-5 to fix bdi congested.
- Rename 0001-drbd-Support-zeroout-device-in-initial-sync.patch
to 0001-Support-zeroout-device-in-initial-sync.patch
- Add update-to-8.4.6-5.patch
* Fri Sep 25 2015 [email protected]
- BSC#947460, add rcdrbd symlink.
* Wed Aug 19 2015 [email protected]
- Fate#317940, merge patch set into one patch.
- Support zeroout/discard-devices instead of zap-devices
- New feature flag FF_DISCARD
- Add patch 0001-drbd-Support-zeroout-device-in-initial-sync.patch
- Remove old patch set:
Patch 0000-cover-letter-fate317940.patch
Patch 0001-drbd-Fix-the-wrong-logic-of-moving-history.patch
Patch 0002-drbd-Add-options-zap_devices-to-new-current-uuid.patch
Patch 0003-drbd-A-function-to-zero-out-drbd-backing-device.patch
Patch 0004-drbd-New-packet-P_ZERO_OUT.patch
Patch 0005-drbd-Functions-to-notify-peer-node-to-start.patch
Patch 0006-drbd-Wapper-for-zeroing-out-device-by-worker.patch
Patch 0007-drbd-Flags-for-background-drbd-device-work.patch
Patch 0008-drbd-Function-to-work-with-packet-P_ZERO_OUT.patch
Patch 0009-drbd-Receive-zero-out-command-from-peer-node.patch
Patch 0010-drbd-Handle-new-current-uuid-zap-devices.patch
* Wed Jul 29 2015 [email protected]
- BSC#939778. Add obsolete of old packages and a description for
KMP package.
- Require kernel-source-rt for RT.
* Mon Jul 20 2015 [email protected]
- Fate#317940. Speed up initial sync by supporting zero out
device.
Patch 0000-cover-letter-fate317940.patch
Patch 0001-drbd-Fix-the-wrong-logic-of-moving-history.patch
Patch 0002-drbd-Add-options-zap_devices-to-new-current-uuid.patch
Patch 0003-drbd-A-function-to-zero-out-drbd-backing-device.patch
Patch 0004-drbd-New-packet-P_ZERO_OUT.patch
Patch 0005-drbd-Functions-to-notify-peer-node-to-start.patch
Patch 0006-drbd-Wapper-for-zeroing-out-device-by-worker.patch
Patch 0007-drbd-Flags-for-background-drbd-device-work.patch
Patch 0008-drbd-Function-to-work-with-packet-P_ZERO_OUT.patch
Patch 0009-drbd-Receive-zero-out-command-from-peer-node.patch
Patch 0010-drbd-Handle-new-current-uuid-zap-devices.patch
- Delete useless patch init-script-fixes.diff
- ExcludeArch i586 and s390, since user space split into
drbd-utils.
* Fri Apr 17 2015 [email protected]
- Update to 8.4.6
- With DRBD module version 8.4.5, we split out the management tools
into their own repository. Started out as "drbd-utils version
8.9.0". To manage DRBD 8.4.5 kernel modules and above, want
drbd-utils >= 8.9.0
- fix failing of user space helpers since kernel 3.13. This bug is
known as 'out of mem, failed to invoke fence-peer helper'
- fix connection timeouts for resources with multiple volumes
- fix an issue with DRBD on linux software raid by properly
remapping bi_bdev
- fix a (hard to trigger) race condition between promoting to primary
an connection handshake. In case the bug was hit the Primary got
stuck in WFBitmapS connection state
- Fix a NULL deref when resuming IO on a diskless primary
- Fix compile issues with uncommon architectures
- improvements to asender performance. With high end backing storage
and networking equipment you may see IOPS improvements between
25% to 50%.
- Highest number on a single drbd seen by LINBIT so far: 160000 IOPS
- backport of events2 and status commands from drbd9. This allows
to be DRBD9 compatible starting with this release, and to get used
to DRBD9 compatible status reporting
- support for lsblk in drbd
- Update to 8.4.5
- fix potential BUG_ON in mempool_alloc for older kernels (<2.6.23)
- fix cornercase of resync finished detection
- fix drbd_ldev_destroy to run exactly once and in worker context
- fix spurious detach/disconnect: don't announce WRITE_SAME
- fix NULL pointer deref in blk_add_request_payload
- (DISCARD/TRIM handling in sd)
- fix regression: potential NULL pointer dereference
- fix regression: potential list corruption
- fix regression: potential deadlock in adm functions (drbdsetup)
- fix regression: /sbin vs /usr/sbin in scripts
- fix race stopping the worker thread
- new debugfs presence expose oldest requests and other details
- userspace moved to own repository
- linux 3.13 and 3.14 compatibility
- improve adaptive resync controler
- reduce bitmap IO during resync
- allow write-ordering policy to be bumped up again
- trigger tcp_flush_pending_frames() for PING/PING_ACK
- fix potential segfault in drbdadm adjust
- drbdsetup improvements: fix netlink socket buffers; detect
modprobe failure
/lib/modules/6.4.0-150600.21-default /lib/modules/6.4.0-150600.21-default/updates /lib/modules/6.4.0-150600.21-default/updates/drbd.ko /lib/modules/6.4.0-150600.21-default/updates/drbd_transport_tcp.ko
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Jul 9 20:22:04 2024