glozow ba7c67f609
Merge bitcoin/bitcoin#29879: fuzz: explicitly cap the vsize of RBFs for diagram checks
016ed248ba0ae64e3f0c93bb47a2cd9b5e49cd85 fuzz: explicitly cap the vsize of RBFs for diagram checks (Greg Sanders)

Pull request description:

  In master we are hitting a case where vsize transactions much larger than max standard size are causing an overflow in not-yet-exposed RBF diagram checking code: https://github.com/bitcoin/bitcoin/pull/29757#issuecomment-2049220195

  `ConsumeTxMemPoolEntry` is creating entries with tens of thousands of sigops cost, causing the resulting RBFs to be "overly large".

  To fix this I cause the fuzz test to stop adding transactions to the mempool when we reach a potential overflow of `int32_t`.

ACKs for top commit:
  glozow:
    ACK 016ed248ba0ae64e3f0c93bb47a2cd9b5e49cd85
  marcofleon:
    ACK 016ed248ba0ae64e3f0c93bb47a2cd9b5e49cd85. I ran libFuzzer on `package_rbf` on the current master branch until the overflow was encountered. Then I built the PR branch and ran the fuzzer using the crash input.

Tree-SHA512: b3ffc98d2c4598eb3010edd58b9370aab1441aafbb1044c83b2b90c17dfe9135b8de9dba475dd0108863c1ffedede443cd978e95231a41cf1f0715629197fa51
2024-04-22 12:33:06 +01:00
..
2023-11-14 17:41:54 +01:00
2023-12-06 15:44:38 +01:00
2023-11-21 13:15:44 +00:00
2024-01-09 15:15:36 -03:00
2024-03-18 10:32:00 -04:00
2023-11-30 11:28:19 +01:00
2023-11-07 10:21:51 +09:00
2023-11-21 13:15:44 +00:00
2024-02-29 14:13:58 -03:00
2023-03-23 19:38:38 +01:00
2023-01-26 10:44:05 +01:00
2023-11-30 11:28:19 +01:00
2023-12-07 11:06:16 +01:00
2023-11-30 11:27:54 +01:00
2023-11-30 11:28:19 +01:00
2023-11-30 11:28:19 +01:00
2023-11-30 11:28:19 +01:00