From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 382CE1FF0DD for ; Thu, 22 Oct 2026 21:38:20 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 75468214CB; Thu, 22 Oct 2026 21:38:19 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stoiko Ivanov Subject: applied: [PATCH zfsonlinux 0/2] fix #8178, #7653 Date: Thu, 22 Oct 2026 21:38:03 +0200 Message-ID: <179269787503.3524145.8642722857663884737.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261020140319.1240275-1-s.ivanov@proxmox.com> References: <20261020140319.1240275-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792697895456 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.506 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: SP7DT5LEAJZUJUREN2SSRNKOQIZ3WVET X-Message-ID-Hash: SP7DT5LEAJZUJUREN2SSRNKOQIZ3WVET X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 20 Oct 2026 16:02:32 +0200, Stoiko Ivanov wrote: > 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. > > [...] Applied, thanks! [1/2] fix #8178: d/patches: add patches already queued for zfs-2.4.5 commit: c1da06e6a9b3be4982997aaff532e8688af3c2fd [2/2] fix #7653: d/patches: cherry-pick fix for stale page-cache on receive/rollback commit: 9ec8ca7076d660a1c37b37fb90cf126a46713de4