diff options
| author | Kent Overstreet <kent.overstreet@gmail.com> | 2020-01-04 22:09:52 +0100 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-10-22 23:08:34 +0200 |
| commit | e7808eef95213678a5c4d009aef636e9037588fb (patch) | |
| tree | b87a3de82e1f2dc77f7585b1d7b9e2b87ccb4d1a /fs/bcachefs/error.h | |
| parent | bcachefs: Hacky fixes for device removal (diff) | |
| download | linux-e7808eef95213678a5c4d009aef636e9037588fb.tar.xz linux-e7808eef95213678a5c4d009aef636e9037588fb.zip | |
bcachefs: Kill bch2_fs_bug()
These have all been converted to fsck/inconsistent errors
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/error.h')
| -rw-r--r-- | fs/bcachefs/error.h | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/fs/bcachefs/error.h b/fs/bcachefs/error.h index 7dcb0f6552fc..de319794ccd1 100644 --- a/fs/bcachefs/error.h +++ b/fs/bcachefs/error.h @@ -17,26 +17,6 @@ struct work_struct; /* Error messages: */ /* - * Very fatal logic/inconsistency errors: these indicate that we've majorly - * screwed up at runtime, i.e. it's not likely that it was just caused by the - * data on disk being inconsistent. These BUG(): - * - * XXX: audit and convert to inconsistent() checks - */ - -#define bch2_fs_bug(c, ...) \ -do { \ - bch_err(c, __VA_ARGS__); \ - BUG(); \ -} while (0) - -#define bch2_fs_bug_on(cond, c, ...) \ -do { \ - if (cond) \ - bch2_fs_bug(c, __VA_ARGS__); \ -} while (0) - -/* * Inconsistency errors: The on disk data is inconsistent. If these occur during * initial recovery, they don't indicate a bug in the running code - we walk all * the metadata before modifying anything. If they occur at runtime, they |