From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-kernel 2/2] bump version to 6.5.11-6
Date: Wed, 29 Nov 2023 10:27:25 +0100 [thread overview]
Message-ID: <20231129092727.862143-3-f.gruenbichler@proxmox.com> (raw)
In-Reply-To: <20231129092727.862143-1-f.gruenbichler@proxmox.com>
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Makefile | 2 +-
debian/changelog | 6 ++++++
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index f0d119c..991e39e 100644
--- a/Makefile
+++ b/Makefile
@@ -6,7 +6,7 @@ KERNEL_MIN=5
KERNEL_PATCHLEVEL=11
# increment KREL for every published package release!
# rebuild packages with new KREL and run 'make abiupdate'
-KREL=5
+KREL=6
KERNEL_MAJMIN=$(KERNEL_MAJ).$(KERNEL_MIN)
KERNEL_VER=$(KERNEL_MAJMIN).$(KERNEL_PATCHLEVEL)
diff --git a/debian/changelog b/debian/changelog
index 646728e..e5442aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+proxmox-kernel-6.5 (6.5.11-6) bookworm; urgency=medium
+
+ * cherry-pick ZFS fix for (rare) dirty dnode data corruption bug
+
+ -- Proxmox Support Team <support@proxmox.com> Wed, 29 Nov 2023 09:32:26 +0100
+
proxmox-kernel-6.5 (6.5.11-5) bookworm; urgency=medium
* properly set CONFIG_VFIO_VIRQFD as a boolean
--
2.39.2
next prev parent reply other threads:[~2023-11-29 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 9:27 [pve-devel] (already applied) [PATCH zfsonlinux/kernel 0/4] Fix ZFS data corruption bug Fabian Grünbichler
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 ` Fabian Grünbichler [this message]
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-3-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.