[master] b262392 Force reload of VSC segments until we know what the remapping bug is or replace the code wholesale, whichever comes first.
Poul-Henning Kamp
phk at FreeBSD.org
Mon Jun 12 16:35:10 CEST 2017
commit b2623920d6a4aac53163e9ec1e5af97303f80107
Author: Poul-Henning Kamp <phk at FreeBSD.org>
Date: Mon Jun 12 14:33:27 2017 +0000
Force reload of VSC segments until we know what the remapping bug is
or replace the code wholesale, whichever comes first.
diff --git a/lib/libvarnishapi/vsc.c b/lib/libvarnishapi/vsc.c
index 4cc91f3..737af89 100644
--- a/lib/libvarnishapi/vsc.c
+++ b/lib/libvarnishapi/vsc.c
@@ -473,7 +473,8 @@ VSC_Iter(struct vsm *vd, struct VSM_fantom *fantom, VSC_iter_f *func,
struct vsc_pt *pt;
int i;
- if (VSM_valid != VSM_StillValid(vd, &vsc->iter_fantom)) {
+ /* XXX: workaround: Force reload */
+ if (1 || VSM_valid != VSM_StillValid(vd, &vsc->iter_fantom)) {
/* Tell app that list will be nuked */
(void)func(priv, NULL);
vsc_build_vf_list(vd);
More information about the varnish-commit
mailing list