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

elfuse segfaults before its first vCPU exists under a 1.5 TiB RLIMIT_AS

Abierto
  • ¿Algo no está bien?
#459 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, macos
Área
operating-systems

Línea de trabajo

Start with the startup trace around src/core/bootstrap.c:710 and inspect the code between build_linux_stack and hv_vcpu_create; the issue leaves the faulting instruction and whether Hypervisor.framework is responsible unresolved. Reproduce on macOS 26.4.1 with ulimit -v at 1.5 TiB, then compare with 6 TiB and macOS 27. Done means the fault is identified and elfuse either boots or exits with an error instead of segfaulting.

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

Descripción

Background

#448's test-rlimit-seed lane starts elfuse under a host ulimit -v, and at 1.5 TiB it exited 139 on the macOS 26.4.1 CI runner. Draft PR #457 found two separate crashes behind that; #458 has the full background and the table of runs. This issue is the one at 1.5 TiB, where guest memory is set up but boot never reaches the guest.

Intention

Under a host address-space limit that leaves too little room for a vCPU, elfuse should fail with an error and a non-zero exit, or boot, not segfault. The first step is to find what faults.

Evidence

Same #457 job and runner as #458: macOS 26.4.1 (25E253), Mac16,10 (M4), 24 GiB, ELFUSE_STARTUP_TRACE=1. Under ulimit -v 1.5 TiB, busybox true, --verbose busybox cat /proc/self/limits and test-proc-limits all exited 139, and so did the original lane case in 3 of 3 repeats and when run outside a command substitution. elfuse --version exited 0. At 6 TiB every run exited 0.

The slab fits and boot gets through build_linux_stack; the trace line for hv_vcpu_create (src/core/bootstrap.c:710) never appears:

startup primary_mmap                    0.700 ms
startup cow_shm_upgrade                 1.361 ms
startup hv_vm_map                       2.560 ms
startup guest_init                      4.695 ms
...
startup vdso_build                      0.002 ms
startup build_linux_stack               0.011 ms
Segmentation fault: 11

At 6 TiB the same trace continues with startup hv_vcpu_create 0.437 ms and the guest runs.

hv_vcpu_create is wrapped in HV_CHECK, which prints a crash report when the call returns an error, and none was printed.

Not confirmed:

  • Which instruction faults. The runner left no crash report under ~/Library/Logs/DiagnosticReports for these processes.
  • Whether the fault is inside Hypervisor.framework. The missing HV_CHECK report suggests hv_vcpu_create faults rather than returns an error when the limit leaves it no room, but the code between build_linux_stack and that call is not ruled out.
  • Why this needs so much address space on macOS 26. On macOS 27 (M-series) the same build boots under 1.5 TiB.

Refs #448, #457, #458

Lenguaje dominante
C
Estrellas
275
Forks
29
Merge medio
2 d 8 h
PR fusionados (30 d)
17

Preparar el entorno

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 sysprog21/elfuse

Todos los issues de sysprog21/elfuse

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.