nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-10 13:13:44 +01:00
Code Issues Packages Projects Releases Wiki Activity

sched: Allow the new sched to react to new cons

Browse Source
This commit is contained in:
Matt Traudt 2017-09-19 19:06:13 -04:00
parent ac73913d40
commit a8c54ce581
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
changes/bug23537 Normal file
View File

@ -0,0 +1,4 @@
o Minor bugfixes (scheduler):
- When switching schedulers due to a consensus change, we didn't give the new
scheduler a chance to react to the consensus. Fix that. Fixes bug 23537;
bugfix on 0.3.2.1-alpha

5
src/or/scheduler.c
View File

@ -371,12 +371,13 @@ void
scheduler_notify_networkstatus_changed(const networkstatus_t *old_c, scheduler_notify_networkstatus_changed(const networkstatus_t *old_c,
const networkstatus_t *new_c) const networkstatus_t *new_c)
{ {
/* Maybe the consensus param made us change the scheduler. */
set_scheduler();
/* Then tell the (possibly new) scheduler that we have a new consensus */ /* Then tell the (possibly new) scheduler that we have a new consensus */
if (the_scheduler->on_new_consensus) { if (the_scheduler->on_new_consensus) {
the_scheduler->on_new_consensus(old_c, new_c); the_scheduler->on_new_consensus(old_c, new_c);
} }
/* Maybe the consensus param made us change the scheduler. */
set_scheduler();
} }
/* /*