all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lucas Barros <lucasbarros.kam@gmail.com>
Subject: applied: [PATCH common] fix #8288: file: read first line: treat ESRCH like a missing file
Date: Thu, 12 Nov 2026 00:05:00 +0100	[thread overview]
Message-ID: <179443829789.1755154.3896377866586127101.b4-ty@b4> (raw)
In-Reply-To: <20261109142501.23212-1-lucasbarros.kam@gmail.com>

On Mon, 09 Nov 2026 11:25:01 -0300, Lucas Barros wrote:
> Opening a file below /proc/<pid>/ can fail with ESRCH instead of ENOENT
> when the process exits and gets reaped while the path is looked up, as
> the permission check on the /proc/<pid> directory then no longer finds
> the task. file_read_first_line() only treats ENOENT as "does not
> exist" and dies otherwise.
> 
> This is hit by check_process_running(), which polls /proc/<pid>/stat
> via read_proc_pid_stat(). On boot, startall uses it to wait for the
> start workers of each startup order, outside of any eval, so a worker
> exiting at the wrong moment aborts startall: pve-guests.service fails
> and guests of later startup orders are not started at all.
> 
> [...]

Applied, thanks!

[1/1] fix #8288: file: read first line: treat ESRCH like a missing file
      commit: c9d3e0637b918f3803a98d1fa99838a882f16373




      reply	other threads:[~2026-11-11 23:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 14:25 [PATCH common] fix #8288: file: read first line: treat ESRCH like a missing file Lucas Barros
2026-11-11 23:05 ` 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=179443829789.1755154.3896377866586127101.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=lucasbarros.kam@gmail.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal