Lines Matching full:error

3 bcachefs private error codes
6 In bcachefs, as a hard rule we do not throw or directly use standard error
7 codes (-EINVAL, -EBUSY, etc.). Instead, we define private error codes as needed
10 This gives us much better error messages and makes debugging much easier. Any
11 direct uses of standard error codes you see in the source code are simply old
14 Private error codes may subtype another error code, this allows for grouping of
16 errors), as well as specifying which standard error code should be returned at
19 At the module boundary, we use bch2_err_class() to convert to a standard error
20 code; this also emits a trace event so that the original error code be
23 Do not reuse error codes! Generally speaking, a private error code should only
27 Try to give error codes names that are as reasonably descriptive of the error
28 as possible. Frequently, the error will be logged at a place far removed from
29 where the error was generated; good names for error codes mean much more
30 descriptive and useful error messages.