From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Subject: [pve-devel] applied: [PATCH ceph reef-stable-8] bluefs: fix OSD crash caused by incorrect alignment assertion
Date: Wed, 14 Jan 2026 09:57:56 +0100 [thread overview]
Message-ID: <176838078159.2016253.9744229034550295398.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260107104422.2919586-2-k.chai@proxmox.com>
On Wed, 07 Jan 2026 18:41:46 +0800, Kefu Chai wrote:
> A regression was introduced in PR #62174 that added a `ceph_assert()`
> statement which incorrectly assumes alloc_unit is always aligned. This
> causes OSD crashes when the assertion fails.
>
> This cherry-pick removes the faulty assertion, resolving the crash while
> maintaining correct functionality for both aligned and unaligned alloc_unit
> values.
>
> [...]
Applied, but ammended the commit to actually add the patch to the quilt series
file, so that it's picked up by the debian build system and fixed the -22 lines
offset of the diff hunk, thanks!
btw. as the final reef release 18.2.8 is being planned (again), and should be
ready soon after the ceph lab is up again after their DC move, do you think
this should be released earlier or could it be fine to wait a bit.
FWIW, we could upload just the ceph-osd packages for now, or are there other
daemons affected by this fix?
[1/1] bluefs: fix OSD crash caused by incorrect alignment assertion
commit: 59bb899d8398575768b6ddd9dc7f4eabd0018533
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-14 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 10:41 [pve-devel] " Kefu Chai
2026-01-14 7:47 ` Kefu Chai
2026-01-14 8:57 ` Thomas Lamprecht [this message]
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=176838078159.2016253.9744229034550295398.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=k.chai@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.