On Tue, 7 May 2024 15:41:03 +0800 (CST) <xu.xi...@zte.com.cn> wrote: > From: Peilin He <he.pei...@zte.com.cn> > > Introduce a tracepoint for icmp_send, which can help users to get more > detail information conveniently when icmp abnormal events happen. > > 1. Giving an usecase example: > ============================= > When an application experiences packet loss due to an unreachable UDP > destination port, the kernel will send an exception message through the > icmp_send function. By adding a trace point for icmp_send, developers or > system administrators can obtain detailed information about the UDP > packet loss, including the type, code, source address, destination address, > source port, and destination port. This facilitates the trouble-shooting > of UDP packet loss issues especially for those network-service > applications. > > 2. Operation Instructions: > ========================== > Switch to the tracing directory. > cd /sys/kernel/tracing > Filter for destination port unreachable. > echo "type==3 && code==3" > events/icmp/icmp_send/filter > Enable trace event. > echo 1 > events/icmp/icmp_send/enable > > 3. Result View: > ================ > udp_client_erro-11370 [002] ...s.12 124.728002: > icmp_send: icmp_send: type=3, code=3. > From 127.0.0.1:41895 to 127.0.0.1:6666 ulen=23 > skbaddr=00000000589b167a > > Signed-off-by: Peilin He <he.pei...@zte.com.cn> > Signed-off-by: xu xin <xu.xi...@zte.com.cn> > Reviewed-by: Yunkai Zhang <zhang.yun...@zte.com.cn> > Cc: Yang Yang <yang.yan...@zte.com.cn> > Cc: Liu Chun <liu.ch...@zte.com.cn> > Cc: Xuexin Jiang <jiang.xue...@zte.com.cn> > ---
From just a tracing point of view: Reviewed-by: Steven Rostedt (Google) <rost...@goodmis.org> -- Steve
