From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 977FE1FF0AF for ; Fri, 20 Nov 2026 09:35:04 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A6070216DD; Fri, 20 Nov 2026 09:35:02 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, =?UTF-8?q?Michael=20K=C3=B6ppl?= 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 Message-ID: <179516362215.3505452.3707075202732762445.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261119141302.600137-1-m.koeppl@proxmox.com> References: <20261119141302.600137-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795163698617 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.149 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: UFCSJYYKCAEE3GUAG3QREGVQ4NTZZGAV X-Message-ID-Hash: UFCSJYYKCAEE3GUAG3QREGVQ4NTZZGAV X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: l.sichert@proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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