David Bidner, le mar. 22 sept. 2026 05:34:34 +0200, a ecrit: > > Since entry is released, you need to read the vme_next field before calling > > vm_map_coalesce_entry, just like we do for current->vme_next.
Oops, I missed that "entry" is filled by vm_map_lookup_entry in all cases. > > Also, I guess we can avoid doing this when vm_map_coalesce_entry returned > > false? > > With a non-empty range, the loop can already have freed the start entry. Ok. Samuel
