all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] (already applied) [PATCH zfsonlinux/kernel 0/4] Fix ZFS data corruption bug
Date: Wed, 29 Nov 2023 10:27:23 +0100	[thread overview]
Message-ID: <20231129092727.862143-1-f.gruenbichler@proxmox.com> (raw)

cherry-picked from upstream's staging-2.2.2 and verified using the
reproducer script on an affected machine.

kernel side (actual fix):

Fabian Grünbichler (2):
  update zfs to 2.2.0-pve4
  bump version to 6.5.11-6

 Makefile              | 2 +-
 debian/changelog      | 6 ++++++
 submodules/zfsonlinux | 2 +-
 3 files changed, 8 insertions(+), 2 deletions(-)

zfs userspace (for version consistency/reduced confusion):

Fabian Grünbichler (2):
  cherry-pick fix for data corruption
  bump version to 2.2.0-pve4

 debian/changelog                              |  7 ++
 ...heck-dnode-and-its-data-for-dirtines.patch | 97 +++++++++++++++++++
 debian/patches/series                         |  1 +
 3 files changed, 105 insertions(+)
 create mode 100644 debian/patches/0018-dnode_is_dirty-check-dnode-and-its-data-for-dirtines.patch

-- 
2.39.2





             reply	other threads:[~2023-11-29  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  9:27 Fabian Grünbichler [this message]
2023-11-29  9:27 ` [pve-devel] [PATCH pve-kernel 1/2] update zfs to 2.2.0-pve4 Fabian Grünbichler
2023-11-29  9:27 ` [pve-devel] [PATCH pve-kernel 2/2] bump version to 6.5.11-6 Fabian Grünbichler
2023-11-29  9:27 ` [pve-devel] [PATCH zfsonlinux 1/2] cherry-pick fix for data corruption Fabian Grünbichler
2023-11-29  9:27 ` [pve-devel] [PATCH zfsonlinux 2/2] bump version to 2.2.0-pve4 Fabian Grünbichler

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=20231129092727.862143-1-f.gruenbichler@proxmox.com \
    --to=f.gruenbichler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal