WireGuard for the Linux kernel https://git.zx2c4.com/wireguard-linux/atom/fs/bcachefs/bkey_methods.h?h=update-toolchain 2024-08-14T03:00:50Z 2024-08-14T03:00:50Z Kent Overstreet kent.overstreet@linux.dev 2024-08-13T01:31:25Z urn:sha1:d97de0d017cde0d442c3d144b4f969f43064cc0f bkey_fsck_err() was added as an interface that looks like fsck_err(), but previously all it did was ensure that the appropriate error counter was incremented in the superblock. This is a cleanup and bugfix patch that converts it to a wrapper around fsck_err(). This is needed to fix an issue with the upgrade path to disk_accounting_v3, where the "silent fix" error list now includes bkey_fsck errors; fsck_err() handles this in a unified way, and since we need to change printing of bkey fsck errors from the caller to the inner bkey_fsck_err() calls, this ends up being a pretty big change. Als,, rename .invalid() methods to .validate(), for clarity, while we're changing the function signature anyways (to drop the printbuf argument). Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-06-19T22:27:23Z Kent Overstreet kent.overstreet@linux.dev 2024-06-12T23:51:15Z urn:sha1:d47df4f616d523b4ef832d03ec28b2e6d838067b We use 0 size arrays as markers, but ubsan doesn't know that - cast them to a pointer to fix the splat. Also, make sure this code gets tested a bit more. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-05-09T20:23:36Z Kent Overstreet kent.overstreet@linux.dev 2024-05-08T22:40:42Z urn:sha1:65eaf4e24ab6b4809491248e1fed36b8d49c1ea9 We're about to start using bch_validate_flags for superblock section validation - it's no longer bkey specific. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-05-08T21:29:18Z Kent Overstreet kent.overstreet@linux.dev 2024-04-07T22:05:34Z urn:sha1:5dd8c60e1e044816d789098ce2454a130e06b03d Combine iter/update/trigger/str_hash flags into a single enum, and x-macroize them for a to_text() function later. These flags are all for a specific iter/key/update context, so it makes sense to group them together - iter/update/trigger flags were already given distinct bits, this cleans up and unifies that handling. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-21T11:01:45Z Kent Overstreet kent.overstreet@linux.dev 2024-01-07T22:14:46Z urn:sha1:38c23fb809f60bda1adfc431b18200b8f68c2025 Add a new flag to be explicit about when we're running atomic triggers. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-06T04:24:20Z Kent Overstreet kent.overstreet@linux.dev 2024-01-01T02:01:06Z urn:sha1:f0431c5f474643a0dbe9f3c288480422abd16179 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-06T04:24:19Z Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:54:52Z urn:sha1:c95e9ec48682425267e682e5489ee9dc42313335 New flag so that triggers can distinguish whether we're running transactional or atomic triggers (or gc) - unifying the callbacks. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-06T04:24:19Z Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:44:50Z urn:sha1:089e311347ebe347a79545ca117a02811623c91e dead code Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-06T04:24:19Z Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:19:09Z urn:sha1:ad00bce07da8138c08f6585f153412b65c99b064 Prep work for disk space accounting rewrite: we're going to want to use a single callback for both of our current triggers, so we need to change them to have the same type signature first. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-01-06T04:24:19Z Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:19:09Z urn:sha1:717296c34c8d9d13d7aad4d710b0c3bdb285783b Prep work for disk space accounting rewrite: we're going to want to use a single callback for both of our current triggers, so we need to change them to have the same type signature first. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>