public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH zfsonlinux 0/2] fix #8178, #7653
Date: Tue, 20 Oct 2026 16:02:32 +0200	[thread overview]
Message-ID: <20261020140319.1240275-1-s.ivanov@proxmox.com> (raw)

Both issues seem to have found fixes upstream recently.
for #7653 this is a single commit merged to upstream master [0], which
can be picked to 2.4.4 cleanly,
while for #8178 there were a few clean-ups upstream, which are already
queued up for 2.4.5 upstream [1].

I picked all patches applied to zfs-2.4.5-staging upstream for #8178, as
they were either a prerequisite for a clean pick of the fix or did not
seem too invasive.

minimally tested on 2 VMs with replicated guests, but did not manage or try
to reproduce the reported issues.

[0] https://github.com/openzfs/zfs/pull/19013
[1] https://github.com/openzfs/zfs/pull/19244

Stoiko Ivanov (2):
  fix #8178: d/patches: add patches already queued for zfs-2.4.5
  fix #7653: d/patches: cherry-pick fix for stale page-cache on
    receive/rollback

 ...the-project-ID-for-every-object-type.patch | 209 +++++++++
 ...thin-a-single-directory-under-projec.patch |  74 ++++
 ...t-ID-inheritance-and-renames-within-.patch | 208 +++++++++
 ...uf_hdr-s-anon-state-invariant-checks.patch | 113 +++++
 ...-support-for-building-akmod-packages.patch | 344 +++++++++++++++
 ...k-delivery-of-SIGUSR1-in-send_worker.patch |  93 ++++
 ...I-baseline-naming-on-RHEL-to-prevent.patch | 417 ++++++++++++++++++
 ...ader-destruction-for-in-flight-L2-wr.patch | 119 +++++
 ...2HDR-in-arc_release-for-in-flight-wr.patch | 174 ++++++++
 ...etween-arc_release-and-arc_read_done.patch | 179 ++++++++
 ...inux-drop-cached-pages-in-zfs_rezget.patch |  53 +++
 debian/patches/series                         |  11 +
 12 files changed, 1994 insertions(+)
 create mode 100644 debian/patches/0011-Inherit-the-project-ID-for-every-object-type.patch
 create mode 100644 debian/patches/0012-Allow-renames-within-a-single-directory-under-projec.patch
 create mode 100644 debian/patches/0013-ZTS-check-project-ID-inheritance-and-renames-within-.patch
 create mode 100644 debian/patches/0014-arc-harness-buf_hdr-s-anon-state-invariant-checks.patch
 create mode 100644 debian/patches/0015-rpm-Add-support-for-building-akmod-packages.patch
 create mode 100644 debian/patches/0016-libzfs_core-block-delivery-of-SIGUSR1-in-send_worker.patch
 create mode 100644 debian/patches/0017-kmodtool-use-kABI-baseline-naming-on-RHEL-to-prevent.patch
 create mode 100644 debian/patches/0018-L2ARC-Reorder-header-destruction-for-in-flight-L2-wr.patch
 create mode 100644 debian/patches/0019-L2ARC-Preserve-L2HDR-in-arc_release-for-in-flight-wr.patch
 create mode 100644 debian/patches/0020-arc-fix-race-between-arc_release-and-arc_read_done.patch
 create mode 100644 debian/patches/0021-Linux-drop-cached-pages-in-zfs_rezget.patch

-- 
2.47.3





             reply	other threads:[~2026-10-20 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 14:02 Stoiko Ivanov [this message]
2026-10-20 14:02 ` [PATCH zfsonlinux 1/2] fix #8178: d/patches: add patches already queued for zfs-2.4.5 Stoiko Ivanov
2026-10-20 14:02 ` [PATCH zfsonlinux 2/2] fix #7653: d/patches: cherry-pick fix for stale page-cache on receive/rollback Stoiko Ivanov

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=20261020140319.1240275-1-s.ivanov@proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pve-devel@lists.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal