• Dridi Boukelmoune's avatar
    vsm: Do not store MAP_FAILED in a VSM segment · ba7bf7ff
    Dridi Boukelmoune authored
    The problem is that a MAP_FAILED segment ends up in its vsm_set::segs
    list, at which point NULL checks will determine what to do with the
    segment, and MAP_FAILED != NULL.
    
    This can happen when winning (or losing?) the race with a VSC segment
    that goes away after being found in the index, but before being mapped.
    
    One surefire result is a crash in vsm_unmapseg() tripping on assertions
    that other fields are also not NULL. There may be other unidentified ill
    effects.
    ba7bf7ff
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
bin Loading commit data...
contrib Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
vmod Loading commit data...
.dir-locals.el Loading commit data...
.editorconfig Loading commit data...
.gitignore Loading commit data...
.lgtm.yml Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...
vsc.am Loading commit data...
vtc.am Loading commit data...
wflags.py Loading commit data...