From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <s.ivanov@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E80BC895D5 for <pve-devel@lists.proxmox.com>; Mon, 17 Oct 2022 20:10:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D16A421DB9 for <pve-devel@lists.proxmox.com>; Mon, 17 Oct 2022 20:10:10 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Mon, 17 Oct 2022 20:10:10 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id EBE9744A5E for <pve-devel@lists.proxmox.com>; Mon, 17 Oct 2022 20:10:09 +0200 (CEST) From: Stoiko Ivanov <s.ivanov@proxmox.com> To: pve-devel@lists.proxmox.com Date: Mon, 17 Oct 2022 20:09:50 +0200 Message-Id: <20221017180952.1574207-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.178 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH zfsonlinux 0/2] add patches already on zfs-2.1.7-staging upstream X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Mon, 17 Oct 2022 18:10:11 -0000 While discussing whether to push the 2.1.6 packages further we noticed that a small glitch happened on debian-upstream. Our build should not be affected (we don't ship init-scripts), but syncing the changes could help in a few corner cases (user installed 2.1.6-1 from debian-upstream and then changed to our repositories is the one situation I think might cause issues) The remaining patches were included due to being quite limited in what they do. minimally tested on 2 VMs of mine with the current tip of pve-kernel/master and on a hardware machine with ZFS on / Stoiko Ivanov (2): cherry-pick a few patches from zfs-2.1.7-staging install zfs-load-key.service ...ramfs-use-mount.zfs-instead-of-mount.patch | 74 +++++++++++++++++++ .../0013-etc-mask-zfs-load-key.service.patch | 37 ++++++++++ ...ould-have-its-argument-list-marked-v.patch | 40 ++++++++++ debian/patches/series | 3 + debian/zfsutils-linux.install | 1 + 5 files changed, 155 insertions(+) create mode 100644 debian/patches/0012-initramfs-use-mount.zfs-instead-of-mount.patch create mode 100644 debian/patches/0013-etc-mask-zfs-load-key.service.patch create mode 100644 debian/patches/0014-kcfpool_alloc-should-have-its-argument-list-marked-v.patch -- 2.30.2