From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id DBEEA1FF138 for ; Wed, 18 Feb 2026 19:33:11 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A4E1C3C99; Wed, 18 Feb 2026 19:34:11 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: partially-applied: [PATCH-SERIES cluster v2 0/2] cfs lock: small improvements Date: Wed, 18 Feb 2026 19:33:49 +0100 Message-ID: <177143961735.4093791.9170054059025936239.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260218154438.184685-1-f.ebner@proxmox.com> References: <20260218154438.184685-1-f.ebner@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: 1771439639913 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.020 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: 453YPEFRY5VGSTIJ7RPVSVJD6FUWJVND X-Message-ID-Hash: 453YPEFRY5VGSTIJ7RPVSVJD6FUWJVND 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 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 Wed, 18 Feb 2026 16:44:28 +0100, Fiona Ebner wrote: > Changes in v2: > * Add patch to improve how signals are handled. > > Because of a recent report in the forum [0], I wanted to ping the v1 > of the submission [1], which could've helped in this case. > > During re-testing, I ran into another issue and noticed that signals > are not nicely handled yet, so there is a second patch now :) > > [...] Applied the first one for now, thanks! [1/2] cfs lock: attempt to acquire lock more frequently commit: 13a71af58bd3ecad3be9b960ae12e3de6343585c