From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Subject: applied: [PATCH manager] fix #8195: api: ceph: mds: lock ceph.conf when changing MDS sections
Date: Wed, 28 Oct 2026 18:27:54 +0100 [thread overview]
Message-ID: <179320847186.1870597.11021651003058091341.b4-ty@b4> (raw)
In-Reply-To: <20261026075604.1101150-1-k.chai@proxmox.com>
On Mon, 26 Oct 2026 15:56:04 +0800, Kefu Chai wrote:
> createmds and destroymds read, modify and write ceph.conf without the
> cfs lock, so concurrent tasks can lose each other's changes. E.g.
> destroying two MDS in parallel can leave one section behind, blocking
> that ID from being reused.
>
> Take the lock for each update, as the monitor code does. The createmds
> error path runs after the lock was released, so it only removes the
> section if it still names this node.
>
> [...]
Applied, thanks!
[1/1] fix #8195: api: ceph: mds: lock ceph.conf when changing MDS sections
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=6acb938bd9b1d43c94b2396c540ef27c1634a19c
prev parent reply other threads:[~2026-10-28 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 7:56 [PATCH manager] fix #8195: api: ceph: mds: lock ceph.conf when changing MDS sections Kefu Chai
2026-10-28 17:27 ` 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=179320847186.1870597.11021651003058091341.b4-ty@b4 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox