diff options
| author | Sean Anderson <[email protected]> | 2024-10-18 15:00:37 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2024-10-29 07:54:06 +0000 |
| commit | 68b6dbf1f441c4eba3b8511728a41cf9b01dca35 (patch) | |
| tree | 4eb452797a551e5c56b54374e381fafb0560acd5 /lib/xarray.c | |
| parent | dma-mapping: use trace_dma_alloc for dma_alloc* instead of using trace_dma_map (diff) | |
| download | kernel-68b6dbf1f441c4eba3b8511728a41cf9b01dca35.tar.gz kernel-68b6dbf1f441c4eba3b8511728a41cf9b01dca35.zip | |
dma-mapping: trace more error paths
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 <[email protected]>
Reviewed-by: Steven Rostedt (Google) <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'lib/xarray.c')
0 files changed, 0 insertions, 0 deletions