diff options
| author | David S. Miller <davem@davemloft.net> | 2017-12-20 22:00:26 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-12-20 22:00:26 +0300 |
| commit | b2597f78d4831f2be288b220fcce5c4a9a63abec (patch) | |
| tree | 503a12a1a7357e7b0935fa321ae878a850febb3c /net/ipv4/udp_tunnel.c | |
| parent | 9ee1942cb3a8e1f9d413eaa34221d1a70ee13146 (diff) | |
| parent | cbabf46364b27d08335fef37ecd7a8b89a1c8e07 (diff) | |
| download | linux-b2597f78d4831f2be288b220fcce5c4a9a63abec.tar.xz | |
Merge branch 'replace-tcp_set_state-tracepoint-with-inet_sock_set_state'
Yafang Shao says:
====================
replace tcp_set_state tracepoint with inet_sock_set_state
According to the discussion in the mail thread
https://patchwork.kernel.org/patch/10099243/,
tcp_set_state tracepoint is renamed to inet_sock_set_state tracepoint and is
moved to include/trace/events/sock.h.
With this new tracepoint, we can trace AF_INET/AF_INET6 sock state transitions.
As there's only one single tracepoint for inet, so I didn't create a new trace
file named trace/events/inet_sock.h, and just place it in
include/trace/events/sock.h
Currently TCP/DCCP/SCTP state transitions are traced with this tracepoint.
- Why not more protocol ?
If we really think that anonter protocol should be traced, I will modify the
code to trace it.
I just want to make the code easy and not output useless information.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/udp_tunnel.c')
0 files changed, 0 insertions, 0 deletions