diff options
| author | fanquake <fanquake@gmail.com> | 2021-10-22 19:07:28 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2021-10-22 19:22:44 +0800 |
| commit | 788909f3c79c00501c9e1656bdd685444c98255a (patch) | |
| tree | e134e0f9f1689654c6ca60bb115d08b8bfcfb283 /test/sanitizer_suppressions/ubsan | |
| parent | c001da306b29c46ef1e7421002c3aba3ff5ed514 (diff) | |
| parent | fa2662c293ec0aaa93092b59b6632f74729c4283 (diff) | |
| download | bitcoin-788909f3c79c00501c9e1656bdd685444c98255a.tar.xz | |
Merge bitcoin/bitcoin#23042: net: Avoid logging AlreadyHaveTx when disconnecting misbehaving peer
fa2662c293ec0aaa93092b59b6632f74729c4283 net: Avoid logging AlreadyHaveTx when disconnecting misbehaving peer (MarcoFalke)
Pull request description:
There is no need to log `AlreadyHaveTx` for an inv when a peer is marked for disconnection due to sending that inv. In fact, I find it confusing that a `block-relay-only` connection calls `AlreadyHaveTx` at all. Also there is no need to call `AddKnownTx` when the peer is marked for disconnection.
ACKs for top commit:
naumenkogs:
ACK fa2662c293ec0aaa93092b59b6632f74729c4283
jnewbery:
Code review ACK fa2662c293ec0aaa93092b59b6632f74729c4283
dunxen:
Concept and code review ACK fa2662c293ec0aaa93092b59b6632f74729c4283
Tree-SHA512: 9996b807a824021f992b5281d82ff0cbbe6a442c2fedf7dfd6adda64ccc5e0ef4fb0ff91ab75086f975837bbbb7a5934ac7e671a80dcababa7203c92fc0c7f84
Diffstat (limited to 'test/sanitizer_suppressions/ubsan')
0 files changed, 0 insertions, 0 deletions