From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux] pick bug-fixes staged for 2.2.1
Date: Fri, 17 Nov 2023 17:39:00 +0100 [thread overview]
Message-ID: <09b51d87-b3eb-44d0-acb9-f96e6e045a5f@proxmox.com> (raw)
In-Reply-To: <20231117140302.1210995-1-s.ivanov@proxmox.com>
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.ivanov@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!
prev parent reply other threads:[~2023-11-17 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:03 [pve-devel] " Stoiko Ivanov
2023-11-17 16:39 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09b51d87-b3eb-44d0-acb9-f96e6e045a5f@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox