From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ur; Thu May 18 05:29:57 EDT 2017 Message-ID: Date: Thu, 18 May 2017 11:29:50 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] Re: tsemaquire In-Reply-To: CAHL7psE9KE9zoibYeA09yV4RWq3nAbd7TaA9-_O_Ds0x_rZbXg@mail.gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: webscale proxy HTTP proxy descriptor basically, portclock dequeued the timer and then called the timer function. so just calling timerdel() isnt enougth to disable the timer. as the timer could already have been dequeued and running. the fix i linked keeps track of the completion of the timer function, making timerdel() wait until it returned in case it got run. -- cinap