mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-24 22:58:50 +01:00
When marking guard state instances on a channel, don't mark NULL
It's okay for guard_state to be null: we might have a fallback circuit, or we might not be using guards. Fixes bug 211228; bugfix on 0.3.0.1-alpha
This commit is contained in:
parent
09a00a2f82
commit
35d8270942
2 changed files with 10 additions and 1 deletions
5
changes/bug21128
Normal file
5
changes/bug21128
Normal file
|
@ -0,0 +1,5 @@
|
|||
o Minor bugfixes (client, entry guards):
|
||||
- Fix a bug warning (with backtrace) when we fail a channel
|
||||
that circuits to fallback directories on it. Fixes bug 21128;
|
||||
bugfix on 0.3.0.1-alpha.
|
||||
|
|
@ -2172,7 +2172,11 @@ entry_guard_chan_failed(channel_t *chan)
|
|||
continue;
|
||||
|
||||
origin_circuit_t *origin_circ = TO_ORIGIN_CIRCUIT(circ);
|
||||
entry_guard_failed(&origin_circ->guard_state);
|
||||
if (origin_circ->guard_state) {
|
||||
/* We might have no guard state if we didn't use a guard on this
|
||||
* circuit (eg it's for a fallback directory). */
|
||||
entry_guard_failed(&origin_circ->guard_state);
|
||||
}
|
||||
} SMARTLIST_FOREACH_END(circ);
|
||||
smartlist_free(pending);
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue