summaryrefslogtreecommitdiff
path: root/fs/bcachefs/Kconfig
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2023-07-07 09:42:28 +0300
committerKent Overstreet <kent.overstreet@linux.dev>2023-10-23 00:10:06 +0300
commit067d228bb0c40542620398ef1d79f00f47c05cbb (patch)
tree41402dddcd6aa5921eec83a4917c584d3a920e19 /fs/bcachefs/Kconfig
parent78328fec704e316b36142a9a13af8665cd46da47 (diff)
downloadlinux-067d228bb0c40542620398ef1d79f00f47c05cbb.tar.xz
bcachefs: Enumerate recovery passes
Recovery and fsck have many different passes/jobs to do, which always run in the same order - but not all of them run all the time. Some are for fsck, some for unclean shutdown, some for version upgrades. This adds some new structure: a defined list of recovery passes that we can run in a loop, as well as consolidating the log messages. The main benefit is consolidating the "should run this recovery pass" logic, as well as cleaning up the "this recovery pass has finished" state; instead of having a bunch of ad-hoc state bits in c->flags, we've now got c->curr_recovery_pass. By consolidating the "should run this recovery pass" logic, in the future on disk format upgrades will be able to say "upgrading to this version requires x passes to run", instead of forcing all of fsck to run. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/Kconfig')
0 files changed, 0 insertions, 0 deletions