[prev in list] [next in list] [prev in thread] [next in thread]
List: varnish-bugs
Subject: Re: [Varnish] #1488: Panic at high volume of requests
From: "Varnish" <varnish-bugs () varnish-cache ! org>
Date: 2014-04-28 13:27:02
Message-ID: 065.f2be171a36fa341d7187ce9b2ad19310 () varnish-cache ! org
[Download RAW message or body]
#1488: Panic at high volume of requests
--------------------------+-----------------------------------------------
Reporter: mattrobenolt | Owner: Martin Blix Grydeland <martin@…>
Type: defect | Status: closed
Priority: normal | Milestone:
Component: varnishd | Version: 4.0.0
Severity: normal | Resolution: fixed
Keywords: panic |
--------------------------+-----------------------------------------------
Changes (by Martin Blix Grydeland <martin@…>):
* status: new => closed
* owner: => Martin Blix Grydeland <martin@…>
* resolution: => fixed
Comment:
In [94a3d071b66d4f7aa7f94660cad42e4d58f25724]:
{{{
#!CommitTicketReference repository=""
revision="94a3d071b66d4f7aa7f94660cad42e4d58f25724"
Close race on req->wrk clearing introduced in 6f2e1bcd
The disembarking thread would clear the req->wrk pointer in
CNT_Request. The req could have already been rescheduled on another
worker at this point, causing the req->wrk to be cleared while
processing. Change back to not clearing the pointer for
REQ_FSM_DISEMBARK (it's already been done under mutex in HSH_Lookup
anyways).
Fixes: #1488
}}}
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1488#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic