Dmitry Safonov 96be3dcd01 net/tcp: Add tcp-md5 and tcp-ao tracepoints
Instead of forcing userspace to parse dmesg (that's what currently is
happening, at least in codebase of my current company), provide a better
way, that can be enabled/disabled in runtime.

Currently, there are already tcp events, add hashing related ones there,
too. Rasdaemon currently exercises net_dev_xmit_timeout,
devlink_health_report, but it'll be trivial to teach it to deal with
failed hashes. Otherwise, BGP may trace/log them itself. Especially
exciting for possible investigations is key rotation (RNext_key
requests).

Suggested-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Dmitry Safonov <0x7f454c46@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2024-06-12 06:39:04 +01:00
..
2024-05-29 09:25:15 -07:00
2024-05-18 10:32:39 -07:00
2024-06-10 18:02:14 -07:00
2024-06-05 10:18:06 +01:00
2024-02-20 15:32:45 +01:00
2024-06-10 11:54:18 +01:00
2024-01-11 10:07:29 -08:00
2024-05-28 07:27:29 -07:00
2024-06-10 17:40:26 -07:00
2024-05-18 10:32:39 -07:00
2024-05-16 09:47:45 +01:00
2024-05-23 13:51:09 -07:00
2024-06-10 17:40:26 -07:00
2024-01-31 16:41:16 -08:00