Changelog for drbd-kmp-default-9.0.30~1+git.8e9c0812_k6.2.9_4-11.6.x86_64.rpm :

* Sat Mar 11 2023 Heming Zhao - drbd: fix build error against kernel v6.2.1 (bsc#1209168)
* update patch + bsc-1206791-05-prandom_u32_max.patch
* Fri Jan 06 2023 Heming Zhao - remove useless patch, dax_get_by_host() was replaced by fs_dax_get_by_bdev()
* bsc-1192929_06-dax_support.patch
* Thu Jan 05 2023 Heming Zhao - drbd: fix build error against kernel v6.1.1 (bsc#1206791)
* update bsc-1201335_06-bdi.patch commit log (no code change) + bsc-1201335_06-bdi.patch
* update bsc-1202600_02-dax-introduce-DAX_RECOVERY_WRITE-dax-access-mode.patch (no code change) + bsc-1202600_02-dax-introduce-DAX_RECOVERY_WRITE-dax-access-mode.patch
* using upstream patch to replace exist patch - bsc-1204596_02-drbd-stop-using-bdevname-in-drbd_report_io_error.patch + bsc-1204596_02-drbd-remove-usage-of-bdevname.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 + bsc-1206791-03-drbd-fix-warning-about-initializing-multiple-struct-.patch + bsc-1206791-04-blk_queue_split__no_present.patch + bsc-1206791-05-prandom_u32_max.patch + bsc-1206791-06-write_zeroes__no_capable.patch + bsc-1206791-07-drbd-fix-use-after-free-bugs-in-get_initial_state.patch + bsc-1206791-08-lib-lru_cache-Fixed-array-overflow-caused-by-incorre.patch + bsc-1206791-09-pmem-use-fs_dax_get_by_bdev-instead-of-dax_get_by_ho.patch
* Mon Dec 05 2022 Ludwig Nussel - BuildRequire %kernel_module_package_buildreqs (boo#1205149)
* Sat Oct 22 2022 Heming Zhao - drbd: build error against kernel v6.0.2 (bsc#1204596) - add patch: + bsc-1204596_01-block-remove-blk_cleanup_disk.patch + bsc-1204596_02-drbd-stop-using-bdevname-in-drbd_report_io_error.patch
* Tue Aug 23 2022 Heming Zhao - drbd: build error against kernel v5.19 (bsc#1202600) - add patch: + bsc-1202600_01-remove-QUEUE_FLAG_DISCARD.patch + bsc-1202600_02-dax-introduce-DAX_RECOVERY_WRITE-dax-access-mode.patch + bsc-1202600_03-block-decouple-REQ_OP_SECURE_ERASE-from-REQ_OP_DISCA.patch + bsc-1202600_04-remove-assign_p_sizes_qlim.patch - For rpmbuild warning, modify symlink /usr/sbin/rcdrbd to relative path + drbd.spec
* Fri Jul 08 2022 Heming Zhao - drbd: build error against kernel v5.18 (bsc#1201335) - remove patch: + move_bdi_from_request_queue_to_gendisk.patch - change exist patches name from bsc#1192929: old name: make_block_holder_optional.patch move_kvmalloc_related_to_slab.patch polling_to_bio_base.patch pass_gend_to_blk_queue_update_readahead.patch dax_support.patch add_disk_error_handle.patch have_void_drbd_submit_bio.patch remove_bdgrab.patch new name: 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_06-dax_support.patch bsc-1192929_07-add_disk_error_handle.patch bsc-1192929_08-have_void_drbd_submit_bio.patch bsc-1192929_09-remove_bdgrab.patch - add 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
* Mon Nov 22 2021 nick wang - bsc#1192929, compat to kernel v5.15- Remove patch convert_to_blk_alloc_disk.patch (upstream)- Add patch make_block_holder_optional.patch Add patch move_kvmalloc_related_to_slab.patch Add patch polling_to_bio_base.patch Add patch pass_gend_to_blk_queue_update_readahead.patch Add patch move_bdi_from_request_queue_to_gendisk.patch Add patch dax_support.patch Add patch add_disk_error_handle.patch Add patch have_void_drbd_submit_bio.patch Add patch remove_bdgrab.patch
* Wed Jul 21 2021 nick wang - Update to 9.0.30~1
* 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 compat_genl_maxattr_in_ops.patch- Delete _servicedata file since not used
* Fri Jun 11 2021 nick wang - Correct the real version 9.0.29~1- Disable _servicedata to avoid verbose commits log
* Fri Jun 04 2021 varkolyAATTsuse.com- Update to version 9.1.2
* drbd: fix termination of verify with stop sector
* drbd: Fix locking for the drbd_devices idr
* drbd: use DEFINE_MUTEX insteadm of mutex_init()
* drbd: remove device_to_minor()
* drbd: fix race condition resetting resync_next_bit
* build: fix make; make clean; make; with pre-packaged compat.patch
* compat: fix compat implementation of CRYPTO_TFM_NEED_KEY
* drbd: remove non-existant argument from kerneldoc
* drbd: kernel-doc and related fixes from upstream
* drbd: Avoid comma separated statements
* Fri May 07 2021 nick wang - 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- Add patch compat_genl_maxattr_in_ops.patch (48526a0f) Remove patch drbd-fix-zero-metadata-limit-by-page-size-misaligned.patch Remove patch compat_remove_include_vermagic.patch Remove patch compat-test-header.patch Remove patch submit-bio-private-date.patch Remove patch compat_remove_kernel_setsockopt.patch Remove patch compat_blk_queue_stack_limits.patch Remove patch remove_bdi_cap_stable_writes.patch Remove patch compat_get_fs.patch Remove patch compat_to_v5_11.patch Modify patch suse-coccinelle.patch- cocci apply: linux-5.12.0-2 queue_discard_zeroes_data__no_present (48920ff2a5a9)
* Fri Mar 12 2021 nick wang - bsc#1183429, compat to kernel v5.11 Add patch compat_to_v5_11.patch
* Wed Dec 09 2020 nick wang - 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 nick wang - 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- Remove patch rely-on-sb-handlers.patch (187bddac0) Remove patch fix-err-of-wrong-return-type.patch (969310232) Remove patch compat_remove_pgprot_88dca4c.patch (ee025dc84) 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)- Modify patch compat_remove_kernel_setsockopt.patch (518846b54) Modify patch compat_blk_queue_stack_limits.patch (edaa9b0f2)
* Tue Nov 03 2020 nick wang - bsc#1178388, build error with -Wreturn-type Add patch fix-err-of-wrong-return-type.patch
* Tue Oct 20 2020 nick wang - bsc#1177910, compat to 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- Add tumbleweed only patch Add patch compat_blk_queue_stack_limits.patch
* Fri Sep 18 2020 nick wang - bsc#1175257, 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- Add compatible patches to kernel v5.8.0 Add patch compat_remove_include_vermagic.patch Add patch compat_remove_kernel_setsockopt.patch Add patch compat_remove_pgprot_88dca4c.patch
* Wed Jun 10 2020 nick wang - 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 nick wang - jsc#11801, enable buildrt for Leap15.2 but Tumbleweed.
* Tue Mar 10 2020 nick wang - 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 nick wang - 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 nick wang - bsc#1159786, fix build issue against v5.5 add patch without_pr_warning.patch