Skip to content

Commit e3b3125

Browse files
committed
Merge #19470: banlist: log post-swept banlist size at startup
0b8ba84 banlist: log post-swept banlist size at startup (fanquake) Pull request description: We are currently logging the size of the banlist from before `SweepBanned()` has been called, meaning the value may be incorrect. i.e banlist.dat had `1`ban. That ban is swept on startup. We log "loaded 1 banned node..". Actual banlist size is `0`. ACKs for top commit: jonatack: Code review ACK 0b8ba84 `m_banned` is set in SetBanned and is updated by SweepBanned before the logging. laanwj: Code review ACK 0b8ba84 jnewbery: Code review ACK 0b8ba84 Tree-SHA512: 1d6e363d6c68d7cc214dd685df3d2d27572f6a58a4c0e43c03cfbb03bc01badb6a10ecae403d137094bb316d27f33feb6be15b4e23ef1e9496cd0b3c23c21698
2 parents 6b48c30 + 0b8ba84 commit e3b3125

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/banman.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ BanMan::BanMan(fs::path ban_file, CClientUIInterface* client_interface, int64_t
2626
SweepBanned(); // sweep out unused entries
2727

2828
LogPrint(BCLog::NET, "Loaded %d banned node ips/subnets from banlist.dat %dms\n",
29-
banmap.size(), GetTimeMillis() - n_start);
29+
m_banned.size(), GetTimeMillis() - n_start);
3030
} else {
3131
LogPrintf("Invalid or missing banlist.dat; recreating\n");
3232
SetBannedSetDirty(true); // force write

0 commit comments

Comments
 (0)