summaryrefslogtreecommitdiff
path: root/fs/bcachefs/journal_seq_blacklist.h
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@gmail.com>2022-01-04 19:41:23 -0500
committerKent Overstreet <kent.overstreet@linux.dev>2023-10-22 17:09:21 -0400
commit9b6e2f1e7036d639ca07434fdb27a739b37beb76 (patch)
treefc8face8364f78b93caad20a59ada370d578e9b7 /fs/bcachefs/journal_seq_blacklist.h
parent03ea3962ab99adf0cf7de9949716e6baeda230f3 (diff)
Revert "bcachefs: Delete some obsolete journal_seq_blacklist code"
This reverts commit f95b61228efd04c9c158123da5827c96e9773b29. It turns out, we're seeing filesystems in the wild end up with blacklisted btree node bsets - this should not be happening, and until we understand why and fix it we need to keep this code around. Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
Diffstat (limited to 'fs/bcachefs/journal_seq_blacklist.h')
-rw-r--r--fs/bcachefs/journal_seq_blacklist.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/bcachefs/journal_seq_blacklist.h b/fs/bcachefs/journal_seq_blacklist.h
index b4f876a04586..afb886ec8e25 100644
--- a/fs/bcachefs/journal_seq_blacklist.h
+++ b/fs/bcachefs/journal_seq_blacklist.h
@@ -17,4 +17,6 @@ int bch2_blacklist_table_initialize(struct bch_fs *);
extern const struct bch_sb_field_ops bch_sb_field_ops_journal_seq_blacklist;
+void bch2_blacklist_entries_gc(struct work_struct *);
+
#endif /* _BCACHEFS_JOURNAL_SEQ_BLACKLIST_H */