Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

pidfd for a thread or CLONE_VM child never reports exit

未关闭
  • 哪里不对？
#441 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
c
领域
operating-systems

调研方向

Start in src/runtime/forkipc.c, where a VM child's vm_exit_status is published, and find the thread exit path, then check where proc_pidfd_notify_exit is called. Trace how pidfd_set_target binds a pidfd to its task so an exit recorded before that bind is not lost. Done means a pidfd for a thread or CLONE_VM child becomes readable on exit, and an early exit is still reported.

由索引模型根据 Issue 内容生成。

描述

A pidfd that clone or clone3 makes with CLONE_PIDFD for a thread or a CLONE_VM child never becomes readable. No monitor runs for a task with no host pid, and neither the thread exit path nor the site that publishes a VM child's vm_exit_status (src/runtime/forkipc.c) calls proc_pidfd_notify_exit. A guest that polls the pidfd for the child's exit waits forever, where Linux reports POLLIN.

A fix would notify at both exit sites, and record an exit that lands before pidfd_set_target, since the child can finish before the parent binds the pidfd to it.

Raised in review of #421, where clone(CLONE_VM|CLONE_PIDFD) became able to make such a pidfd; before it only clone3 could.

主要语言
C
星标
275
派生
29
平均合并
2 天 8 小时
30 天内合并 PR
17

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

sysprog21/elfuse 的其他 Issue

查看 sysprog21/elfuse 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。