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: [pve-devel] [PATCH zfsonlinux 0/3] update to 2.1.7
Date: Fri,  2 Dec 2022 17:32:50 +0100	[thread overview]
Message-ID: <20221202163253.713806-1-s.ivanov@proxmox.com> (raw)

ZFS 2.1.7 got released yesterday [0]

the bulk of commits are fixes for issues discovered by static
code-analyzers - while the bugs don't seem to have been hit in the wild it
is still an improvment

did some very superficial tests (migrate a container with replicaton
config forth and back, create a snapshot and rollback to it ([1] stood out
to me), and running ztest for 20 minutes).

While updating I also pulled in a change from debian-upstream, and noticed
that libudev-dev (and libaio-dev) was missing as build-depends.

[0] https://github.com/openzfs/zfs/releases/tag/zfs-2.1.7
[1]
https://github.com/openzfs/zfs/pull/14162/commits/52e658edd7afbe66149da6efec467633868ca03c

Stoiko Ivanov (3):
  update zfs submodule to 2.1.7 and refresh patches
  trim: clean up, fix
  d/control: add libudev-dev and libaio-dev to build-depends

 debian/control                                |  2 +
 ...ith-d-dev-disk-by-id-in-scan-service.patch |  2 +-
 ...md-unit-for-importing-specific-pools.patch |  2 +-
 ...-guard-access-to-l2arc-MFU-MRU-stats.patch |  2 +-
 ...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 -
 .../zfsutils-linux/usr/lib/zfs-linux/trim     | 74 ++++++++-----------
 upstream                                      |  2 +-
 10 files changed, 38 insertions(+), 200 deletions(-)
 delete mode 100644 debian/patches/0012-initramfs-use-mount.zfs-instead-of-mount.patch
 delete mode 100644 debian/patches/0013-etc-mask-zfs-load-key.service.patch
 delete mode 100644 debian/patches/0014-kcfpool_alloc-should-have-its-argument-list-marked-v.patch

-- 
2.30.2





             reply	other threads:[~2022-12-02 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 16:32 Stoiko Ivanov [this message]
2022-12-02 16:32 ` [pve-devel] [PATCH zfsonlinux 1/3] update zfs submodule to 2.1.7 and refresh patches Stoiko Ivanov
2022-12-02 16:32 ` [pve-devel] [PATCH zfsonlinux 2/3] trim: clean up, fix Stoiko Ivanov
2022-12-02 16:32 ` [pve-devel] [PATCH zfsonlinux 3/3] d/control: add libudev-dev and libaio-dev to build-depends Stoiko Ivanov
2022-12-06 15:45 ` [pve-devel] applied: [PATCH zfsonlinux 0/3] update to 2.1.7 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=20221202163253.713806-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