]> err.no Git - varnish/commit
projects / varnish / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 65f508d) | patch
Make sure WRK_Flush() always resets w->niov so WRK_Write() does not
authorphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Wed, 23 Jan 2008 09:26:03 +0000 (09:26 +0000)
committerphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Wed, 23 Jan 2008 09:26:03 +0000 (09:26 +0000)
commitf12ddbf5894229504944578c70f98f51e330dc1a
tree3aee1149594b015439bc18c0beab6aed5fa15a30tree | snapshot
parent65f508d14975d12f38b276351d6dd9e24894091ecommit | diff
Make sure WRK_Flush() always resets w->niov so WRK_Write() does not
overrun the w->iov.

Because niov is right after iov in struct worker, it is hard to predict
what the effect of hitting this bug, but "core dump" is almost a given.

I don't think it has been likely to happen a lot however, as it would
require a full complement of HTTP headers or a very fragmented object.

Coverity Scan (CID:7)

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2369 d4fa192b-c00b-0410-8231-f00ffab90ce4
varnish-cache/bin/varnishd/cache_pool.c diff | blob | history
Varnish, the HTTP accelerator