Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#858 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
linux, rust
Área
operating-systems

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
478
Forks
48
Merge medio
1 d 3 h
PR fusionados (30 d)
72

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de voidzero-dev/vite-task

Todos los issues de voidzero-dev/vite-task

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.