From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: partially-applied: [PATCH-SERIES cluster v2 0/2] cfs lock: small improvements
Date: Wed, 18 Feb 2026 19:33:49 +0100 [thread overview]
Message-ID: <177143961735.4093791.9170054059025936239.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260218154438.184685-1-f.ebner@proxmox.com>
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
prev parent reply other threads:[~2026-02-18 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:44 Fiona Ebner
2026-02-18 15:44 ` [PATCH cluster v2 1/2] cfs lock: attempt to acquire lock more frequently Fiona Ebner
2026-02-18 15:44 ` [PATCH cluster v2 2/2] cfs lock: unlock when encountering signal Fiona Ebner
2026-02-18 18:33 ` Thomas Lamprecht
2026-02-19 13:45 ` Fiona Ebner
2026-02-18 18: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=177143961735.4093791.9170054059025936239.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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