Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

drbd-9.0.30~1+git.8e9c0812-1.6 RPM for ppc64

From OpenSuSE Ports Tumbleweed for ppc64

Name: drbd Distribution: openSUSE Tumbleweed
Version: 9.0.30~1+git.8e9c0812 Vendor: openSUSE
Release: 1.6 Build date: Sat Jan 1 16:17:47 2022
Group: Unspecified Build host: obs-power8-04
Size: 57903 Source RPM: drbd-9.0.30~1+git.8e9c0812-1.6.src.rpm
Summary: Linux driver for the "Distributed Replicated Block Device"
DRBD is a distributed replicated block device. It mirrors a block
device over the network to another machine. Think of it as networked
raid 1. It is a building block for setting up clusters.






* 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
  - 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
    * 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
    * 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
    * 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
    * generate new UUID immediately if a primary loses a disk due to an IO
    * 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
    * 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
* Thu Dec 26 2019 nick wang <>
  - bsc#1159333, back port patch for duplicate resync.
    add patch drbd-update-resync-target-s-dagtag.patch
* Mon Dec 16 2019 nick wang <>
  - 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 Richard Brown <>
  - Remove obsolete Groups tag (fate#326485)
* Fri Oct 11 2019 nick wang <>
  - 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 nick wang <>
  - bsc#1151579, fix collinelle default path and always trigger in obs
    Add patch suse-coccinelle.patch
* Tue Sep 17 2019
  - bsc#1146117, disallow dual primaries when not configured.
    Modify patch rely-on-sb-handles.patch
* Tue Sep 10 2019 Jan Engelhardt <>
  - Restore higher summary specifity.
  - Drop old-age %clean, %defattr.
* Mon Sep 09 2019 nick wang <>
  - 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
  - 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
  - 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
  - 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
  - bsc#1118732, split brain handles malfunction when 2 primaries.
  - Add patch rely-on-sb-handlers.patch
* Mon Dec 10 2018
  - 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
  - bsc#1116820, kernel compatible issue of sle15sp1
  - Add patch compat_have_mempool_init.patch
* Fri Oct 26 2018
  - 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
  - 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
    * 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
  - 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
  - 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
  - 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
  - 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.



Generated by rpm2html 1.8.1

Fabrice Bellet, Mon May 9 10:54:15 2022