diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2023-05-26 22:59:07 +0200 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2024-01-01 17:47:39 +0100 |
| commit | 3398124444b90079a09374ab10444cd937b72ae1 (patch) | |
| tree | 9ad0e27b83e3d684b9cf01d57588f412aa1c5997 /fs/bcachefs/trace.h | |
| parent | bcachefs: Improve trace_trans_restart_too_many_iters() (diff) | |
| download | linux-3398124444b90079a09374ab10444cd937b72ae1.tar.xz linux-3398124444b90079a09374ab10444cd937b72ae1.zip | |
bcachefs: Improve trace_trans_restart_would_deadlock
In the CI, we're seeing tests failing due to excessive would_deadlock
transaction restarts - the tracepoint now includes the lock cycle that
occured.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to '')
| -rw-r--r-- | fs/bcachefs/trace.h | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/fs/bcachefs/trace.h b/fs/bcachefs/trace.h index e0c8db352bff..6e2ad6f3db98 100644 --- a/fs/bcachefs/trace.h +++ b/fs/bcachefs/trace.h @@ -1205,10 +1205,11 @@ DEFINE_EVENT(transaction_restart_iter, trans_restart_memory_allocation_failure, TP_ARGS(trans, caller_ip, path) ); -DEFINE_EVENT(transaction_event, trans_restart_would_deadlock, +DEFINE_EVENT(trans_str, trans_restart_would_deadlock, TP_PROTO(struct btree_trans *trans, - unsigned long caller_ip), - TP_ARGS(trans, caller_ip) + unsigned long caller_ip, + const char *cycle), + TP_ARGS(trans, caller_ip, cycle) ); DEFINE_EVENT(transaction_event, trans_restart_would_deadlock_recursion_limit, |