From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Michael Köppl" <m.koeppl@proxmox.com>
Cc: l.sichert@proxmox.com
Subject: applied: (subset) [PATCH common/storage v2 0/4] fix #8286: do not hold inherited locks in volume cleanup workers
Date: Fri, 20 Nov 2026 09:33:55 +0100 [thread overview]
Message-ID: <179516362215.3505452.3707075202732762445.b4-ty@b4> (raw)
In-Reply-To: <20261119141302.600137-1-m.koeppl@proxmox.com>
On Thu, 19 Nov 2026 15:12:58 +0100, Michael Köppl wrote:
> Destroying a VM through the API with a disk on an LVM storage with
> saferemove=1 leaves its VMID locked until the wipe of the disk is done.
> The imgdel worker is forked while the qmdestroy worker holds the
> config lock and inherits the locked file handle. The worker keeps the
> lock held after the qmdestroy worker exited. Re-creating a VM with the
> same VMID fails with a lock timeout in the meantime.
>
> [...]
Applied, thanks!
[common]
[1/4] tools: lock file: add helper to close inherited lock handles
commit: cab7ebd5049f8ebf557308b203d39679e350eeae
[storage]
[2/4] lvm plugin: avoid name collisions with volumes pending removal
commit: 42f2287c4896fb5b85c20fe9f1a2bcd7e372b60a
[3/4] fix #8286: vdisk free: do not hold inherited locks in cleanup worker
commit: 511eca89372a1d0c0441711f683876d8f5b4c431
[4/4] lvm plugin: do not hold inherited locks in cleanup workers
commit: 4a6b6d34a29f0917340f070eaec27125937749ab
prev parent reply other threads:[~2026-11-20 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 14:12 [PATCH common/storage v2 0/4] fix #8286: do not hold inherited locks in volume cleanup workers Michael Köppl
2026-11-19 14:12 ` [PATCH common v2 1/4] tools: lock file: add helper to close inherited lock handles Michael Köppl
2026-11-19 14:13 ` [PATCH storage v2 2/4] lvm plugin: avoid name collisions with volumes pending removal Michael Köppl
2026-11-19 14:13 ` [PATCH storage v2 3/4] fix #8286: vdisk free: do not hold inherited locks in cleanup worker Michael Köppl
2026-11-19 14:13 ` [PATCH storage v2 4/4] lvm plugin: do not hold inherited locks in cleanup workers Michael Köppl
2026-11-20 8:33 ` 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=179516362215.3505452.3707075202732762445.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=l.sichert@proxmox.com \
--cc=m.koeppl@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