From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH zfsonlinux 0/2] add patches already on zfs-2.1.7-staging upstream
Date: Mon, 17 Oct 2022 20:09:50 +0200 [thread overview]
Message-ID: <20221017180952.1574207-1-s.ivanov@proxmox.com> (raw)
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
next reply other threads:[~2022-10-17 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 18:09 Stoiko Ivanov [this message]
2022-10-17 18:09 ` [pve-devel] [PATCH zfsonlinux 1/2] cherry-pick a few patches from zfs-2.1.7-staging Stoiko Ivanov
2022-10-17 18:09 ` [pve-devel] [PATCH zfsonlinux 2/2] install zfs-load-key.service Stoiko Ivanov
2022-10-18 6:41 ` [pve-devel] applied: [PATCH zfsonlinux 0/2] add patches already on zfs-2.1.7-staging upstream Thomas Lamprecht
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=20221017180952.1574207-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