From: bert hubert <bert.hubert@netherlabs.nl>
Date: Thu, 15 Jan 2015 11:50:10 +0000 (+0100)
Subject: we actually deliver MTasker timeouts with the wrong d_tid set. Unknown if this matter... 
X-Git-Tag: rec-3.7.0-rc1~27
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e19a1ced3002a54e543519ed6bf1694260a98cc2;p=thirdparty%2Fpdns.git

we actually deliver MTasker timeouts with the wrong d_tid set. Unknown if this matters anywhere, but it was wrong in any case.
---

diff --git a/pdns/mtasker.cc b/pdns/mtasker.cc
index 605af28813..f92685451b 100644
--- a/pdns/mtasker.cc
+++ b/pdns/mtasker.cc
@@ -330,6 +330,7 @@ template<class Key, class Val>bool MTasker<Key,Val>::schedule(struct timeval*  n
         d_waitstatus=TimeOut;
         d_eventkey=i->key;        // pass waitEvent the exact key it was woken for
         ucontext_t* uc = i->context;
+        d_tid = i->tid;
         ttdindex.erase(i++);                  // removes the waitpoint 
 
         if(swapcontext(&d_kernel, uc)) { // swaps back to the above point 'A'