[Varnish] #1762: VSL API: endless loop and out of memory in vtx_scan() on forced synthetic transactions

[Varnish]

#1762: VSL API: endless loop and out of memory in vtx_scan() on forced synthetic
transactions
----------------------+----------------------------------
 Reporter:  geoff     |       Owner:
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:  Varnish 4.0 release
Component:  varnishd  |     Version:  4.0.3
 Severity:  critical  |  Resolution:
 Keywords:            |
----------------------+----------------------------------

Comment (by slink):

 The interesting bit is that the vtx vxid has the client bit set:

 {{{
 (gdb) frame 8
 #8  0x00007f55851cee17 in vtx_diag_tag (vtx=0x7d24a0, ptr=0x125823fe80,
 reason=0x7f55851dda23 "vxid mismatch")
     at vsl_dispatch.c:1065
 1065    in vsl_dispatch.c
 (gdb) print /x ptr[1]
 $25 = 0xc06305cc
 (gdb) print /x vtx->key.vxid
 $26 = 0x406305cc
 }}}

 Reviewing the code I am pretty sure that the root cause is not in the vsl
 api, but rather the fact that 4.0 logs SLT_Links with the the
 client/backend bits.

 This is fixed in master cfb309cad60e0239bc7168082d73b4ab6b53744a, so I'll
 just port this back to 4.0

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1762#comment:1>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator