kernel/git/stable/linux.git/fs/bcachefs/trace.h, branch master

Remove bcachefs core code

2025-09-29T20:43:52+00:00

bcachefs was marked 'externally maintained' in 6.17 but the code remained to make the transition smoother. It's now a DKMS module, making the in-kernel code stale, so remove it to avoid any version confusion. Link: https://lore.kernel.org/linux-bcachefs/yokpt2d2g2lluyomtqrdvmkl3amv3kgnipmenobkpgx537kay7@xgcgjviv3n7x/T/ Signed-off-by: Linus Torvalds

bcachefs: Kill unused tracepoints

2025-06-16T23:03:52+00:00

Dead code cleanup. Link: https://lore.kernel.org/linux-bcachefs/20250612224059.39fddd07@batman.local.home/ Signed-off-by: Kent Overstreet

bcachefs: btree iter tracepoints

2025-06-16T02:11:55+00:00

We've been seeing some livelock-ish behavior in the index update part of the main write path, and while we've got low level btree path tracepoints, we've been lacking high level btree iterator tracepoints. Signed-off-by: Kent Overstreet

bcachefs: trace_extent_trim_atomic

2025-06-16T02:11:55+00:00

Add a tracepoint for when we insert only part of an extent, due to too many overwrites. Signed-off-by: Kent Overstreet

bcachefs: bch_err_throw()

2025-06-02T16:16:35+00:00

Add a tracepoint for any time we return an error and unwind. Signed-off-by: Kent Overstreet

bcachefs: io_move_evacuate_bucket tracepoint, counter

2025-05-30T05:21:12+00:00

Signed-off-by: Kent Overstreet

bcachefs: trace_io_move_pred

2025-05-30T05:21:12+00:00

Signed-off-by: Kent Overstreet

bcachefs: Improve trace_trans_restart_upgrade

2025-05-22T00:15:11+00:00

- Convert to a 'fs_str' tracepoint that just emits as a string: this lets us build up the tracepoint with a printbuf, using our pretty printers, and they're much easier to manage - Include locks_held, before and after - Include the btree node pointer we failed on (error pointer, null, or real node) Signed-off-by: Kent Overstreet

bcachefs: Add tracepoint, counter for io_move_created_rebalance

2025-05-22T00:14:58+00:00

Internal moves shouldn't add new rebalance_work, but it's been reported that this seems to be happening. Add a tracepoint and counter so we can see what's going on. Signed-off-by: Kent Overstreet

bcachefs: Poison extents that can't be read due to checksum errors

2025-05-22T00:13:19+00:00

Copygc needs to be able to move extents that have bitrotted. We don't want to delete them - in the future we'll have an API for "read me the data even if there's checksum errors", and in general we don't want to delete anything unless the user asks us to. That will require writing it with a new checksum, which means we can't forget that there was a checksum error so we return the correct error to userspace. Rebalance also wants to skip bad extents; we can now use the poison flag for that. This is currently disabled by default, as we want read fua support so that we can distinguish between transient and permanent errors from the device. It may be enabled with the module parameter: poison_extents_on_checksum_error Signed-off-by: Kent Overstreet