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

fspy does not record file accesses of static programs on kernels without process_vm_readv

未关闭
#858 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
linux, rust

调研方向

Start by reading crates/fspy_seccomp_unotify/src/supervisor/handler/arg.rs:47 and the error handling in crates/fspy_seccomp_unotify/src/supervisor/mod.rs:121. Reproduce with cargo test -p fspy --test static_executable on a kernel where process_vm_readv returns ENOSYS, then add or verify fallback behavior for /proc/<pid>/mem and incomplete tracking. Done means static-program file accesses are recorded on affected kernels and the cache does not retain incomplete results.

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

描述

Problem

Some Linux kernels do not have the process_vm_readv system call. On these kernels, fspy does not record the file accesses of static programs. The task shows no error.

If you change a file that a static program read, the cache does not detect the change. Then the vp run command uses the old cached output.

On musl builds, fspy uses seccomp for all programs, so this problem affects every tracked program (not tested).

Affected kernels

The CONFIG_CROSS_MEMORY_ATTACH kernel option adds the process_vm_readv system call. The following kernels do not set this option:

  • Kata Containers guest kernels. Kata builds these kernels from a configuration that has all options off. Then Kata adds only the options that it needs.
  • The default kernel of Apple container. This kernel is the Kata 3.32.0 kernel vmlinux-6.18.35-197. The /proc/config.gz file of this kernel shows # CONFIG_CROSS_MEMORY_ATTACH is not set.

The default value of this option is y. Most distribution kernels set it.

Cause

For static programs, fspy intercepts system calls with seccomp. The supervisor process then reads each path argument from the memory of the program.

  1. The supervisor reads the memory only with the process_vm_readv system call (crates/fspy_seccomp_unotify/src/supervisor/handler/arg.rs:47).
  2. On the affected kernels, the process_vm_readv system call fails with the ENOSYS error.
  3. The supervisor ignores the error and lets the intercepted system call continue (crates/fspy_seccomp_unotify/src/supervisor/mod.rs:121).
  4. fspy does not record the access.

Steps to reproduce

  1. Start a Fedora virtual machine (VM) with Apple container and its default kernel.
  2. In the VM, check out commit b182c9be.
  3. Run cargo test -p fspy --test static_executable.

Result: 9 of 10 tests fail. Only the readdir test passes, because that test does not read the memory of the program. In each failed test, fspy records only the execution of the test program:

Expected accesses to /hello to match, as (actual, expected): [].
All accesses: [Read(".../fspy-test-bin"), Read(".../fspy-test-bin")]

I also tested a child process in the same VM:

  • The process_vm_readv system call fails with the ENOSYS error.
  • A read of the /proc/<pid>/mem file at the same address returns the correct data.

Possible fixes

  1. If the process_vm_readv system call fails with the ENOSYS error, read the /proc/<pid>/mem file with the pread system call. This file does not need the kernel option. Reads of this file use the same permission check as the process_vm_readv system call. I have not tested this fix in fspy.
  2. If the supervisor cannot read an access, do not cache the task. vite-task already does this with the TrackingIncomplete reason when the access channel is full. This fix also covers other read errors, such as permission errors.
主要语言
Rust
星标
478
派生
48
平均合并
1 天 3 小时
30 天内合并 PR
72

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

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

从这里开始

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

voidzero-dev/vite-task 的其他 Issue

查看 voidzero-dev/vite-task 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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