From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH pve-manager] pvescheduler: hold off HUP and CHLD while a child is forked and recorded
Date: Fri, 13 Nov 2026 10:30:54 +0100 [thread overview]
Message-ID: <179456225103.40281.18315281639873811856.b4-ty@b4> (raw)
In-Reply-To: <20260915133636.858359-1-h.laimer@proxmox.com>
On Tue, 15 Sep 2026 15:36:36 +0200, Hannes Laimer wrote:
> A HUP that lands between the fork and recording neither stops nor hands
> over that child, since the hand-over string is built in the HUP handler
> from what is recorded. A CHLD from a child that exits right after the
> fork, before it is recorded, is missed by the reap it triggers and
> cleared only at the next CHLD from an unrelated child.
>
> Hold both signals off until the child is recorded, and once a HUP came
> in fork nothing more, since the hand-over is already put together.
>
> [...]
Applied, thanks!
[1/1] pvescheduler: hold off HUP and CHLD while a child is forked and recorded
commit: d45e600fb36d00a90222f35142a12c3c7f0e8299
prev parent reply other threads:[~2026-11-13 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 13:36 [PATCH pve-manager] pvescheduler: hold off HUP and CHLD while a child is forked and recorded Hannes Laimer
2026-11-13 9:30 ` Wolfgang Bumiller [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=179456225103.40281.18315281639873811856.b4-ty@b4 \
--to=w.bumiller@proxmox.com \
--cc=h.laimer@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 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.