kernel/linux.git/fs/bcachefs/data_update.c, branch linux-rolling-stable

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: Fix missing newlines before ero

2025-06-18T00:45:27+00:00

Signed-off-by: Kent Overstreet

bcachefs: Make check_key_has_snapshot safer

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

Snapshot deletion v2 added sentinal values for deleted snapshots, so "key for deleted snapshot" - i.e. snapshot deletion missed something - is safe to repair automatically. But if we find a key for a missing snapshot we have no idea what happened, and we shouldn't delete it unless we're very sure that everything else is consistent. So hook it up to the new bch2_require_recovery_pass(), we'll now only delete if snapshots and subvolumes have recenlty been checked. 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: Replace rcu_read_lock() with guards

2025-06-01T04:03:12+00:00

The new guard(), scoped_guard() allow for more natural code. Some of the uses with creative flow control have been left. Signed-off-by: Kent Overstreet

bcachefs: Runtime self healing for keys for deleted snapshots

2025-06-01T02:03:17+00:00

If snapshot deletion incorrectly missing some keys and leaves keys for deleted snapshots, that causes a bit of a problem for data move - we can't move an extent for a nonexistent snapshot, because the extent might have to be fragmented, and maintaining correct visibility in child snapshots doesn't work if it doesn't have a snapshot. Previously we'd just skip these keys, but it turns out that causes copygc to spin. So we need runtime self healing, i.e. calling check_key_has_snapshot() from the data move path. Snapshot deletion v2 included sentinal values for deleted snapshot nodes, so this is quite safe. Signed-off-by: Kent Overstreet

bcachefs: Don't unlock trans before data_update_init()

2025-06-01T02:03:17+00:00

data_update_init() does need to do btree operations, delay doing the unlock-before-io. Signed-off-by: Kent Overstreet

bcachefs: Tweak bch2_data_update_init() for stack usage

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

- Separate out a slowpath for bkey_nocow_lock() - Don't call bch2_bkey_ptrs_c() or loop over pointers more than necessary Signed-off-by: Kent Overstreet

bcachefs: Reduce stack usage in data_update_index_update()

2025-05-22T19:13:17+00:00

Separate tracepoint message generation and other slowpath code into non-inline functions, and use bch2_trans_log_str() instead of using a printbuf for our journal message. Signed-off-by: Kent Overstreet

bcachefs: Kill bkey_buf usage in data_update_index_update()

2025-05-22T19:13:17+00:00

Reduce stack usage - bkey_buf has a 96 byte buffer on the stack, but the btree_trans bump allocator works just fine here. Signed-off-by: Kent Overstreet