From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Max R. Carrara" <m.carrara@proxmox.com>
Subject: [pve-devel] applied: [PATCH ceph master v2] pybind/rbd: disable on_progress callbacks to prevent MGR segfaults
Date: Thu, 11 Sep 2025 11:29:36 +0200 [thread overview]
Message-ID: <175758297470.3626754.16253973613463136615.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250910085244.123467-1-m.carrara@proxmox.com>
On Wed, 10 Sep 2025 10:52:41 +0200, Max R. Carrara wrote:
> Currently, *all* MGRs collectively segfault on Ceph v19.2.3 running on
> Debian Trixie if a client requests the removal of an RBD image from
> the RBD trash (#6635 [0]).
>
> After a lot of investigation, the cause of this still isn't clear to
> me; the most likely culprit are some internal changes to Python
> sub-interpreters that happened between Python versions 3.12 and 3.13.
>
> [...]
Applied, thanks!
[1/1] pybind/rbd: disable on_progress callbacks to prevent MGR segfaults
commit: 35f5f7f91776ccba31254fc47e9359b94580b4a0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-11 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 8:52 [pve-devel] " Max R. Carrara
2025-09-11 9:29 ` 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=175758297470.3626754.16253973613463136615.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.carrara@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