From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Robert Obkircher <r.obkircher@proxmox.com>
Subject: [pbs-devel] applied: [PATCH v2 proxmox-backup] fix: avoid loss of concurrent config changes during datastore deletion
Date: Thu, 6 Nov 2025 18:54:12 +0100 [thread overview]
Message-ID: <176245164753.2372822.2246386513034437776.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251103145422.128701-1-r.obkircher@proxmox.com>
On Mon, 03 Nov 2025 15:53:31 +0100, Robert Obkircher wrote:
> Fix a race between the initial reading of the datastore config before
> destroying the datastore and concurrent config changes, by re-reading
> the config in a locked context before removing the just destroyed
> datastore from it.
>
> Previously, the following steps created files in /srv/test2 but
> removed test2 from the configuration:
>
> [...]
Applied, thanks!
[1/1] fix: avoid loss of concurrent config changes during datastore deletion
commit: b9a00e99d091b663a52c3ebadee0fa6460f03ef3
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-11-06 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 14:53 [pbs-devel] " Robert Obkircher
2025-11-06 17:54 ` 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=176245164753.2372822.2246386513034437776.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=r.obkircher@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.