Sean Anderson 245eb0b6bd dma-mapping: trace more error paths ... [ Upstream commit 68b6dbf1f4 ] It can be surprising to the user if DMA functions are only traced on success. On failure, it can be unclear what the source of the problem is. Fix this by tracing all functions even when they fail. Cases where we BUG/WARN are skipped, since those should be sufficiently noisy already. Signed-off-by: Sean Anderson <sean.anderson@linux.dev> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> Signed-off-by: Christoph Hellwig <hch@lst.de> Stable-dep-of: 7e2368a21741 ("dma-debug: don't enforce dma mapping check on noncoherent allocations") Signed-off-by: Sasha Levin <sashal@kernel.org>		2025-09-19 16:35:42 +02:00
..
events	dma-mapping: trace more error paths	2025-09-19 16:35:42 +02:00
misc	NFS: trace: show TIMEDOUT instead of 0x6e	2024-09-01 10:04:55 -04:00
stages	tracing: Add __print_dynamic_array() helper	2025-05-02 07:58:51 +02:00
bpf_probe.h
define_custom_trace.h
define_trace.h
perf.h
syscall.h
trace_custom_events.h
trace_events.h	tracing/ftrace: disable preemption in syscall probe	2024-12-14 20:03:58 +01:00