wireguard-linux/fs/bcachefs/alloc_background.c, branch update-toolchain

bcachefs: Make bkey_fsck_err() a wrapper around fsck_err()

2024-08-14T03:00:50Z

bkey_fsck_err() was added as an interface that looks like fsck_err(), but previously all it did was ensure that the appropriate error counter was incremented in the superblock. This is a cleanup and bugfix patch that converts it to a wrapper around fsck_err(). This is needed to fix an issue with the upgrade path to disk_accounting_v3, where the "silent fix" error list now includes bkey_fsck errors; fsck_err() handles this in a unified way, and since we need to change printing of bkey fsck errors from the caller to the inner bkey_fsck_err() calls, this ends up being a pretty big change. Als,, rename .invalid() methods to .validate(), for clarity, while we're changing the function signature anyways (to drop the printbuf argument). Signed-off-by: Kent Overstreet

bcachefs: Fix bch2_trigger_alloc when upgrading from old versions

2024-08-14T02:56:50Z

bch2_trigger_alloc was assuming that the new key would always be newly created and thus always an alloc_v4 key, but - not when called from btree_gc. Signed-off-by: Kent Overstreet

bcachefs: Fix missing BTREE_TRIGGER_bucket_invalidate flag

2024-07-14T23:00:16Z

This fixes an accounting mismatch for cached data. Signed-off-by: Kent Overstreet

bcachefs: Reduce the scope of gc_lock

2024-07-14T23:00:15Z

gc_lock is now only for synchronization between check_alloc_info and interior btree updates - nothing else Signed-off-by: Kent Overstreet

bcachefs: fsck_err() may now take a btree_trans

2024-07-14T23:00:14Z

fsck_err() now optionally takes a btree_trans; if the current thread has one, it is required that it be passed. The next patch will use this to unlock when waiting for user input. Signed-off-by: Kent Overstreet

bcachefs: Initialize gc buckets in alloc trigger

2024-07-14T23:00:14Z

Needed for online fsck; we need the trigger to initialize newly allocated buckets and generation number changes while gc is running. Signed-off-by: Kent Overstreet

bcachefs: Convert gc to new accounting

2024-07-14T23:00:13Z

Rewrite fsck/gc for the new accounting scheme. This adds a second set of in-memory accounting counters for gc to use; like with other parts of gc we run all trigger in TRIGGER_GC mode, then compare what we calculated to existing in-memory accounting at the end. Signed-off-by: Kent Overstreet

bcachefs: Disk space accounting rewrite

2024-07-14T23:00:13Z

Main part of the disk accounting rewrite. This is a wholesale rewrite of the existing disk space accounting, which relies on percepu counters that are sharded by journal buffer, and rolled up and added to each journal write. With the new scheme, every set of counters is a distinct key in the accounting btree; this fixes scaling limitations of the old scheme, where counters took up space in each journal entry and required multiple percpu counters. Now, in memory accounting requires a single set of percpu counters - not multiple for each in flight journal buffer - and in the future we'll probably also have counters that don't use in memory percpu counters, they're not strictly required. An accounting update is now a normal btree update, using the btree write buffer path. At transaction commit time, we apply accounting updates to the in memory counters, which are percpu counters indexed in an eytzinger tree by the accounting key. Signed-off-by: Kent Overstreet

bcachefs: bch_alloc->stripe_sectors

2024-07-14T23:00:12Z

Add a separate counter to bch_alloc_v4 for amount of striped data; this lets us separately track striped and unstriped data in a bucket, which lets us see when erasure coding has failed to update extents with stripe pointers, and also find buckets to continue updating if we crash mid way through creating a new stripe. Signed-off-by: Kent Overstreet

bcachefs: add capacity, reserved to fs_alloc_debug_to_text()

2024-07-14T23:00:11Z

Signed-off-by: Kent Overstreet