openvmm: virtiofs: inode lookup count wraps to zero at u64::MAX
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- rust
- Área
- operating-systems
Línea de trabajo
Start in vm/devices/virtio/virtiofs/src/inode.rs around lines 236-262: compare lookup/inc_lookup (which use fetch_add) with the neighbouring forget, which already uses AtomicU64::update with saturating_sub. Decide whether the restore path in vm/devices/virtio/virtiofs/src/microvm/state.rs (validate_microvm_state) should also reject an implausible lookup_count, then add a unit test that replays the reproduction steps and asserts the inode survives fs.forget(node_id, 1) followed by get_attr. Done means a lookup at u64::MAX keeps the count saturated and the node stays in InodeMap; run the virtiofs crate tests with cargo test -p virtiofs.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
VirtioFsInode::lookup and VirtioFsInode::inc_lookup increment lookup_count with AtomicU64::fetch_add(1, Ordering::AcqRel), which uses wrapping arithmetic at u64::MAX. When an inode's lookup_count is u64::MAX — reachable directly via microVM saved-state restore without 2^64 live requests — one additional FUSE_LOOKUP, FUSE_READDIRPLUS, or FUSE_LINK wraps lookup_count to 0, allowing the next FUSE_FORGET to evict the still-referenced inode from InodeMap. Found by formal verification.
Root Cause
In vm/devices/virtio/virtiofs/src/inode.rs, both VirtioFsInode::lookup and VirtioFsInode::inc_lookup use fetch_add(1, Ordering::AcqRel) rather than saturating addition, even though VirtioFsInode::forget immediately below already uses AtomicU64::update with saturating_sub:
/// Increments the lookup count.
pub fn lookup(&self, new_path: PathBuf) {
self.lookup_count.fetch_add(1, Ordering::AcqRel);
self.aliases.write().insert(new_path.clone());
let mut path = self.path.write();
*path = new_path;
}
/// Increments the lookup count without updating the path.
///
/// This is used when returning an existing inode in a FUSE reply (e.g., for hard links)
/// where the kernel will track the reference and later send a forget.
pub fn inc_lookup(&self) {
self.lookup_count.fetch_add(1, Ordering::AcqRel);
}
In microVM mode, validate_microvm_state accepts any SavedInode with inode.lookup_count != 0, including u64::MAX, and restores it verbatim into VirtioFsInode::lookup_count.
Consequence
Once lookup_count wraps from u64::MAX to 0, the inode remains in InodeMap with a zero reference count until any FUSE_FORGET(node_id, n) arrives. At that point, Fuse::forget computes 0u64.saturating_sub(n) == 0 and removes the node from InodeMap while the guest still holds active FUSE references to node_id. Subsequent guest operations on node_id fail with EINVAL (request for unknown inode), and in microVM mode save_microvm_state also fails if an open handle still points to the evicted inode (open handle refers to an untracked inode).
Reproduction
- Create a temporary directory containing a file
"f", instantiateVirtioFs::new(dir.path(), None), and look up"f"once to obtainnode_id. - Set that inode's
lookup_counttou64::MAX(simulating a restoredSavedInodewithlookup_count: u64::MAXor cumulative lookups). - Look up
"f"a second time (or callinode.inc_lookup()).lookup_countwraps fromu64::MAXto0. - Call
fs.forget(node_id, 1)and thenfs.get_attronnode_id.forgetevictsnode_idfromInodeMap, andget_attrfails withlx::Error::EINVAL.
Related: #1627.
- Lenguaje dominante
- Rust
- Estrellas
- 848
- Forks
- 63
- Merge medio
- 13 h 37 min
- PR fusionados (30 d)
- 571
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/nvx
-
area: ci
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area: ci
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
openvmm: virtiofs: aggregate synthetic root st_nlink counts single-file shares as subdirectoriesAbiertoarea: openvmm
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
microsoft/nvx#1632 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: openvmm
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/nvx#1628 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: openvmm
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
microsoft/nvx#1629 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/nvx
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
obi1kenobi/cargo-semver-checks#1814 ·
Los mantenedores suelen responder en 1 día
-
community differential help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
hffgzktbcc-blip/ounce-core#489 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Add support for TODO for AIAbiertoneeds triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
pbakaus/impeccable#1560 ·
Los mantenedores suelen responder en 1 día
-
Links broken in documentationAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
pact-foundation/pact-plugins#125 ·