| commit | af580f659caf025c512429210e069c35f6fff4e8 | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Wed Feb 23 11:45:09 2022 +0100 |
| committer | Willy Tarreau <w@1wt.eu> | Wed Feb 23 17:11:33 2022 +0100 |
| tree | f86b0af8f302c6daabc1d4f5176b5799f2ef00ec | |
| parent | b61fccdc3f1ad23597ae1bf330855d115a60b6b5 [diff] |
MINOR: pools: disable redundant poisonning on pool_free() The poisonning performed on pool_free() used to help a little bit with use-after-free detection, but usually did more harm than good in that it was never possible to perform post-mortem analysis on released objects once poisonning was enabled on allocation. Now that there is a dedicated DEBUG_POOL_INTEGRITY, let's get rid of this annoyance which is not even documented in the management manual.