summaryrefslogtreecommitdiff
path: root/fs/bcachefs/alloc_background.c
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2025-05-10 18:21:49 -0400
committerKent Overstreet <kent.overstreet@linux.dev>2025-05-21 20:15:03 -0400
commit68708efcac711946ffeb1803eb54ebaf44675010 (patch)
treec5b7b46fbb7403e3f94dfc5e39e51b2bfa210fae /fs/bcachefs/alloc_background.c
parent878713b5f56aa4b3dce5bdb7f34952a10183b106 (diff)
downloadlinux-next-68708efcac711946ffeb1803eb54ebaf44675010.tar.gz
linux-next-68708efcac711946ffeb1803eb54ebaf44675010.zip
bcachefs: struct bch_fs_recovery
bch_fs has gotten obnoxiously big, let's start organizing thins a bit better. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/alloc_background.c')
-rw-r--r--fs/bcachefs/alloc_background.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/bcachefs/alloc_background.c b/fs/bcachefs/alloc_background.c
index f8d21c12c3d1..4ae2aa6ea758 100644
--- a/fs/bcachefs/alloc_background.c
+++ b/fs/bcachefs/alloc_background.c
@@ -309,7 +309,7 @@ int bch2_alloc_v4_validate(struct bch_fs *c, struct bkey_s_c k,
"data type inconsistency");
bkey_fsck_err_on(!a.io_time[READ] &&
- c->curr_recovery_pass > BCH_RECOVERY_PASS_check_alloc_to_lru_refs,
+ c->recovery.curr_pass > BCH_RECOVERY_PASS_check_alloc_to_lru_refs,
c, alloc_key_cached_but_read_time_zero,
"cached bucket with read_time == 0");
break;