kernel/git/stable/linux.git/fs/bcachefs/chardev.c, branch master

Remove bcachefs core code

2025-09-29T20:43:52+00:00

bcachefs was marked 'externally maintained' in 6.17 but the code remained to make the transition smoother. It's now a DKMS module, making the in-kernel code stale, so remove it to avoid any version confusion. Link: https://lore.kernel.org/linux-bcachefs/yokpt2d2g2lluyomtqrdvmkl3amv3kgnipmenobkpgx537kay7@xgcgjviv3n7x/T/ Signed-off-by: Linus Torvalds

bcachefs: Fix pool->alloc NULL pointer dereference

2025-06-16T23:03:52+00:00

btree_interior_update_pool has not been initialized before the filesystem becomes read-write, thus mempool_alloc in bch2_btree_update_start will trigger pool->alloc NULL pointer dereference in mempool_alloc_noprof Reported-by: syzbot+2f3859bd28f20fa682e6@syzkaller.appspotmail.com Signed-off-by: Alan Huang Signed-off-by: Kent Overstreet

bcachefs: ioctl: avoid stack overflow warning

2025-06-12T03:21:30+00:00

Multiple ioctl handlers individually use a lot of stack space, and clang chooses to inline them into the bch2_fs_ioctl() function, blowing through the warning limit: fs/bcachefs/chardev.c:655:6: error: stack frame size (1032) exceeds limit (1024) in 'bch2_fs_ioctl' [-Werror,-Wframe-larger-than] 655 | long bch2_fs_ioctl(struct bch_fs *c, unsigned cmd, void __user *arg) By marking the largest two of them as noinline_for_stack, no indidual code path ends up using this much, which avoids the warning and reduces the possible total stack usage in the ioctl handler. Signed-off-by: Arnd Bergmann Signed-off-by: Kent Overstreet

bcachefs: bch_err_throw()

2025-06-02T16:16:35+00:00

Add a tracepoint for any time we return an error and unwind. Signed-off-by: Kent Overstreet

bcachefs: Replace rcu_read_lock() with guards

2025-06-01T04:03:12+00:00

The new guard(), scoped_guard() allow for more natural code. Some of the uses with creative flow control have been left. Signed-off-by: Kent Overstreet

bcachefs: for_each_online_member_rcu()

2025-05-22T00:14:26+00:00

Signed-off-by: Kent Overstreet

bcachefs: bch_dev_usage_full

2025-04-02T14:24:34+00:00

All the fastpaths that need device usage don't need the sector totals or fragmentation, just bucket counts. Split bch_dev_usage up into two different versions, the normal one with just bucket counts. This is also a stack usage improvement, since we have a bch_dev_usage on the stack in the allocation path. Signed-off-by: Kent Overstreet

bcachefs: Split up bch_dev.io_ref

2025-04-02T14:24:34+00:00

We now have separate per device io_refs for read and write access. This fixes a device removal bug where the discard workers were still running while we're removing alloc info for that device. It's also a bit of hardening; we no longer allow writes to devices that are read-only. Signed-off-by: Kent Overstreet

bcachefs: Don't use designated initializers for disk_accounting_pos

2025-03-30T20:35:13+00:00

Not all compilers fully initialize these - they're not guaranteed to because of the union shenanigans. Fixes: https://github.com/koverstreet/bcachefs/issues/844 Signed-off-by: Kent Overstreet

bcachefs: Convert migrate to move_data_phys()

2025-03-15T01:02:12+00:00

Iterating over backpointers on a specific device is potentially much cheaper than walking all filesystem data. Signed-off-by: Kent Overstreet