Am 17/11/2023 um 15:03 schrieb Stoiko Ivanov: > ZFS 2.2.1 is currently being prepared, but the 3 patches added here > seem quite relevant, as the might cause dataloss/panics on setups > which run `zpool upgrade`. > See upstreams discussion for 2.2.1: > https://github.com/openzfs/zfs/pull/15498/ > and the most critical issue: > https://github.com/openzfs/zfs/pull/15529 > finally: > https://github.com/openzfs/zfs/commit/459c99ff2339a4a514abcf2255f9b3e5324ef09e > should not hurt either > > the change to the UBSAN patch (0013) is unrelate, cosmetic only and > happened by running export-patchqueue. > > Signed-off-by: Stoiko Ivanov <s.iva...@proxmox.com> > --- > minimally tested by building our current kernel with this and booting it in > 2 VMs - the tunable (module parameter) is present and set to 0 > ...und-UBSAN-errors-for-variable-arrays.patch | 5 +- > ...g-between-unencrypted-and-encrypted-.patch | 44 ++++ > ...Add-a-tunable-to-disable-BRT-support.patch | 201 ++++++++++++++++++ > ...2.1-Disable-block-cloning-by-default.patch | 42 ++++ > debian/patches/series | 3 + > 5 files changed, 291 insertions(+), 4 deletions(-) > create mode 100644 > debian/patches/0015-Fix-block-cloning-between-unencrypted-and-encrypted-.patch > create mode 100644 > debian/patches/0016-Add-a-tunable-to-disable-BRT-support.patch > create mode 100644 > debian/patches/0017-zfs-2.2.1-Disable-block-cloning-by-default.patch > >
applied, thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
