linux.git/fs/bcachefs/btree_write_buffer.c, branch v6.16 Linux kernel source tree bcachefs: Check for bad write buffer key when moving from journal 2025-06-24T19:48:00+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-06-23T22:42:42+00:00 865ad1dbf13244b349e3da2731c1188476ad17b8 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Kill unused tracepoints 2025-06-16T23:03:52+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-06-14T00:06:33+00:00 10dfe4926de30b550913409d107005278ab47911 Dead code cleanup. Link: https://lore.kernel.org/linux-bcachefs/20250612224059.39fddd07@batman.local.home/ Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Dead code cleanup.

Link: https://lore.kernel.org/linux-bcachefs/20250612224059.39fddd07@batman.local.home/
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: bch_err_throw() 2025-06-02T16:16:35+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-05-28T15:57:50+00:00 09b9c72bd4b77a954123997377665fb30f1d07e1 Add a tracepoint for any time we return an error and unwind. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Add a tracepoint for any time we return an error and unwind.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Extra write buffer asserts 2025-05-22T00:14:56+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-05-12T19:14:19+00:00 ac4c7ac90eb7f5ea013b8842b2d803742f4484c0 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: bch_fs.writes -> enumerated_refs 2025-05-22T00:14:27+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-04-18T18:56:09+00:00 c9b1d94a2196fcfd1985ff8728b22abda400b1ac Drop the single-purpose write ref code in bcachefs.h, and convert to enumarated refs. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Drop the single-purpose write ref code in bcachefs.h, and convert to
enumarated refs.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Move various init code to _init_early() 2025-05-22T00:14:02+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-04-05T23:30:43+00:00 a17e985be9831bf866795fe5e3da219d2061ce6c _init_early() is for initialization that cannot fail, and often must happen for teardown partway through initialization to work. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
_init_early() is for initialization that cannot fail, and often must
happen for teardown partway through initialization to work.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Use sort_nonatomic() instead of sort() 2025-04-06T23:33:53+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-03-26T15:44:30+00:00 55fd97fbc4744a43fb2d134908e481266cf33bda Fixes "task out to lunch" warnings during recovery on large machines with lots of dirty data in the journal. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Fixes "task out to lunch" warnings during recovery on large machines
with lots of dirty data in the journal.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Kill btree_iter.trans 2025-04-02T14:24:34+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-03-21T19:18:51+00:00 9180ad2e161b7030e0af78fd2266cbcefe81e652 This was planned to be done ages ago, now finally completed; there are places where we have quite a few btree_trans objects on the stack, so this reduces stack usage somewhat. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
This was planned to be done ages ago, now finally completed; there are
places where we have quite a few btree_trans objects on the stack, so
this reduces stack usage somewhat.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Change btree wb assert to runtime error 2025-03-14T14:25:25+00:00 Kent Overstreet kent.overstreet@linux.dev 2025-03-14T13:54:43+00:00 90fd9ad5b0c981693c8512d9da01f14fb6596e9d We just had a report of the assert for "btree in write buffer for non-write buffer btree" popping during the 6.14 upgrade. - 150TB filesystem, after a reboot the upgrade was able to continue from where it left off, so no major damage. But with 6.14 about to come out we want to get this tracked down asap, and need more data if other users hit this. Convert the BUG_ON() to an emergency read-only, and print out btree, the key itself, and stack trace from the original write buffer update (which did not have this check before). Reported-by: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
We just had a report of the assert for "btree in write buffer for
non-write buffer btree" popping during the 6.14 upgrade.

- 150TB filesystem, after a reboot the upgrade was able to continue from
  where it left off, so no major damage.

But with 6.14 about to come out we want to get this tracked down asap,
and need more data if other users hit this.

Convert the BUG_ON() to an emergency read-only, and print out btree, the
key itself, and stack trace from the original write buffer update (which
did not have this check before).

Reported-by: Stijn Tintel <stijn@linux-ipv6.be>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Assert that btree write buffer only touches the right btrees 2025-01-10T04:38:41+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-12-24T21:57:24+00:00 cb3f34982c9dfccf1aadde4e69043c7da3107c92 More asserts, more better. Also, clean up the per-btree flags a bit. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
More asserts, more better.

Also, clean up the per-btree flags a bit.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>