-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make ctx->vsl not NULL in vcl_init #4046
base: master
Are you sure you want to change the base?
Conversation
A buffer with a zero wid is used as a convenience for non transactional logs, no buffering is actually needed.
This is a common source of panic when vmods functions/methods logging to vsl get called from housekeeping vcl subroutines. Refs varnishcache#2998
My homework submission after bugwash: I agree with the problem statement: VMOD functions/methods which could potentially be called from On the other hand, we need to motivate VMOD developers to produce meaningful CLI errors when
So I would propose:
*1)
|
Taking this as an example is a little bit unfair, because vmod_querystring supports Varnish versions both before and after this was formalized. If I decided to target supported branches only this hack would go away. |
Maybe I have not expressed my intend clearly enough, but I only took your code as an example for the need to log the error messages from all invocations, not just the first. |
This is a common source of panic when vmods functions/methods that log to vsl get called from housekeeping vcl subroutines.
We currently already have
ctx->vsl
set invcl_fini
, this will set it invcl_init
too.