diff options
author | Kent Overstreet <kent.overstreet@gmail.com> | 2022-01-04 19:41:23 -0500 |
---|---|---|
committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-10-22 17:09:21 -0400 |
commit | 9b6e2f1e7036d639ca07434fdb27a739b37beb76 (patch) | |
tree | fc8face8364f78b93caad20a59ada370d578e9b7 /fs/bcachefs/bcachefs.h | |
parent | 03ea3962ab99adf0cf7de9949716e6baeda230f3 (diff) | |
download | lwn-9b6e2f1e7036d639ca07434fdb27a739b37beb76.tar.gz lwn-9b6e2f1e7036d639ca07434fdb27a739b37beb76.zip |
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/bcachefs.h')
-rw-r--r-- | fs/bcachefs/bcachefs.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/bcachefs/bcachefs.h b/fs/bcachefs/bcachefs.h index 8ef874b3afbb..4ebaefd408a4 100644 --- a/fs/bcachefs/bcachefs.h +++ b/fs/bcachefs/bcachefs.h @@ -755,6 +755,7 @@ struct bch_fs { /* JOURNAL SEQ BLACKLIST */ struct journal_seq_blacklist_table * journal_seq_blacklist_table; + struct work_struct journal_seq_blacklist_gc_work; /* ALLOCATOR */ spinlock_t freelist_lock; |