From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH zfsonlinux] update submodule and patches to 2.3.5
Date: Tue, 13 Jan 2026 19:12:59 +0100 [thread overview]
Message-ID: <176832797204.2885556.4483418152664203841.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251124170601.2120680-1-s.ivanov@proxmox.com>
On Mon, 24 Nov 2025 18:05:57 +0100, Stoiko Ivanov wrote:
> after looking through the changelog and discussions.
> the 2 dropped patcher were for 6.17 compatibility, which we needed
> before 2.3.5 was released.
>
> Issues addressed apart from kernel compatibility that might be of
> interest in our usecases:
> * https://github.com/openzfs/zfs/issues/17184 (panic in context of
> many hardlinks/inodes being added)
> * https://github.com/openzfs/zfs/issues/17761 (issue with sync-writes
> for the non-default zvol_use_blk_mq module parameter setting)
>
> [...]
Applied, thanks!
[1/1] update submodule and patches to 2.3.5
commit: 1fbb5bbb21a2bfe48a5a5cec1f2db8d7ec6f77a2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-13 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 17:05 Stoiko Ivanov
2026-01-13 18:12 ` 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=176832797204.2885556.4483418152664203841.b4-ty@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