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] update zfs submodule to 2.2.7 and refresh patches
Date: Wed, 15 Jan 2025 17:05:09 +0100 [thread overview]
Message-ID: <f29e9c7d-dfce-4fad-9f2c-2f9a1fe8035b@proxmox.com> (raw)
In-Reply-To: <20241212170145.1287391-1-s.ivanov@proxmox.com>
Am 12.12.24 um 18:01 schrieb Stoiko Ivanov:
> drop the cherry-picked kernel 6.11 compatibility patches.
>
> this upstream release [0] is a bit larger than usual, and might have a bit
> of potential for regressions.
>
> apart from the compatibilty fixes for newer kernels (up until 6.12),
> fixes to the testsystem,ci and fixes for FreeBSD the following might be
> interesting for our use-cases:
> * 308d04ac3 ("Fix inconsistent mount options for ZFS root")
> * bc0d89bfc ("Fix an uninitialized data access (#16511)")
> * f4e66db40 ("vdev_disk: move abd return and free off the interrupt handler")
> * 0f86fcc2a ("Linux: Fix zfs_prune panics")
> * cf80a803d ("zvol: ensure device minors are properly cleaned up")
> * 299da6ace ("Fix race in libzfs_run_process_impl")
> * 0bd8481aa ("add get_name implementation for exports. (#16833)")
>
> I did some minimal testing on 2 VM's with a few nested containers and
> storage replication, additionally I installed that version on a VM with
> / on ZFS - mostly for checking 308d04ac3 in our environment.
>
> [0] https://github.com/openzfs/zfs/releases/tag/zfs-2.2.7
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> From a quick skim at upstream's channels I think that the release was
> cut due to the 6.12 compatibility patches - but quite a few more things
> were pulled in. More tests would be very much appreciated, and I'd wait
> a few days to see if test upstream show regressions.
>
> debian/patches/0005-Enable-zed-emails.patch | 2 +-
> .../0006-dont-symlink-zed-scripts.patch | 4 +-
> ...0-compat-Fix-tracepoints-definitions.patch | 229 ----
> ...x-array-fields-to-log-record-structs.patch | 979 ------------------
> ...add-flex-array-field-to-TString-type.patch | 103 --
> debian/patches/series | 3 -
> upstream | 2 +-
> 7 files changed, 4 insertions(+), 1318 deletions(-)
> delete mode 100644 debian/patches/0012-Linux-6.10-compat-Fix-tracepoints-definitions.patch
> delete mode 100644 debian/patches/0013-zfs_log-add-flex-array-fields-to-log-record-structs.patch
> delete mode 100644 debian/patches/0014-lua-add-flex-array-field-to-TString-type.patch
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-15 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 17:01 [pve-devel] " Stoiko Ivanov
2025-01-15 11:52 ` Stoiko Ivanov
2025-01-15 16:05 ` 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=f29e9c7d-dfce-4fad-9f2c-2f9a1fe8035b@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