• Nils Goroll's avatar
    initialize PRIV_TASK and PRIV_TOP vmod arguments once per subroutine · f03948f4
    Nils Goroll authored
    ... and fail the VCL unless successful.
    
    Providing the PRIVs to vmods is a core function, so error handling
    should happen outside vmods.
    
    Besides being safe, this initialization can be more efficient than
    previous code for PRIVs used frequently within the same subroutine.
    
    An alternative approach would be to initialize all privs once per
    task / top request, but unless all privs are actually used in a VCL,
    this approach could impose significant overhead, both in terms of time
    and memory. By initializing privs once per sub, we impose overhead for
    privs which are referenced but not actually used in a subroutine, but
    not for all of the vcl.
    
    Fixes #2708
    f03948f4
Name
Last commit
Last update
.github Loading commit data...
bin 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...
.dir-locals.el Loading commit data...
.gitignore 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...