aboutgitcodebugslistschat
path: root/test/tcp
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2026-06-20 01:26:23 +1000
committerStefano Brivio <sbrivio@redhat.com>2026-06-22 09:13:46 +0200
commit780ba8a55feb99feb11c3277b2cb7d3222ec7872 (patch)
tree2b09c2c93041f200b3e2021778f943461197b6fb /test/tcp
parent2fbeb3b1ea2998a1e1a1854aea9fdffcc62a4d15 (diff)
downloadpasst-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar.gz
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar.bz2
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar.lz
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar.xz
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.tar.zst
passt-780ba8a55feb99feb11c3277b2cb7d3222ec7872.zip
flow: Include flow details with higher priority log messages
Currently flow_log() and related functions / macros have a 'details' parameter which indicates whether to add extra messages with details of the flow's addresses. This is still a bit awkward to invoke, and only used in a few places. Change the logic, to automatically include the details if and only if the log priority is greater than LOG_DEBUG. Rationale: If at debug log level, there are already a bunch of debug messages tracking the flow life cycle, which include those details (we make sure to retain those). It's usually pretty easy to cross reference a specific flow debug message with the flow's history including the details. If at higher log level, and we generate a flow-connected error or warning we don't have those life cycle messages. So, just giving the flow index doesn't really tell you anything about which flow tripped the error. Adding the address details make the error message significantly more useful. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/tcp')
0 files changed, 0 insertions, 0 deletions