diff options
| author | Nick Mathewson <nickm@torproject.org> | 2021-05-26 13:02:56 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2021-05-26 13:02:56 -0400 |
| commit | d12b16614d09b303f9ef9624107b589264537341 (patch) | |
| tree | 0cd377212c883b56d91150ebef7e35b2b2b9069f /changes/bug40375 | |
| parent | 4a7379b80a3d0f61d258b26f82d894da9b8cd0f5 (diff) | |
| download | tor-d12b16614d09b303f9ef9624107b589264537341.tar.gz tor-d12b16614d09b303f9ef9624107b589264537341.zip | |
Prefer mmap()ed consensus files over cached_dir_t entries.
Cached_dir_t is a somewhat "legacy" kind of storage when used for
consensus documents, and it appears that there are cases when
changing our settings causes us to stop updating those entries.
This can cause trouble, as @arma found out in #40375, where he
changed his settings around, and consensus diff application got
messed up: consensus diffs were being _requested_ based on the
latest consensus, but were being (incorrectly) applied to a
consensus that was no longer the latest one.
This patch is a minimal fix for backporting purposes: it has Tor do
the same search when applying consensus diffs as we use to request
them. This should be sufficient for correct behavior.
There's a similar case in GETINFO handling; I've fixed that too.
Fixes #40375; bugfix on 0.3.1.1-alpha.
Diffstat (limited to 'changes/bug40375')
| -rw-r--r-- | changes/bug40375 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/bug40375 b/changes/bug40375 new file mode 100644 index 0000000000..7ac32bc628 --- /dev/null +++ b/changes/bug40375 @@ -0,0 +1,5 @@ + o Minor bugfixes (consensus handling): + - Avoid a set of bugs that could be caused by inconsistently preferring + an out-of-date consensus stored in a stale directory cache over + a more recent one stored on disk as the latest consensus. + Fixes bug 40375; bugfix on 0.3.1.1-alpha. |