linux.git/fs/bcachefs/darray.c, branch master Linux kernel source tree Remove bcachefs core code 2025-09-29T20:43:52+00:00 Linus Torvalds torvalds@linux-foundation.org 2025-09-29T20:43:52+00:00 f2c61db29f277b9c80de92102fc532cc247495cd 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 <torvalds@linux-foundation.org> 
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 <torvalds@linux-foundation.org>
bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations 2024-10-20T20:50:14+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-19T22:27:09+00:00 f0d3302073e60b55318c941cd10b225a3cde9d32 kvmalloc() doesn't support allocations > INT_MAX, but vmalloc() does - the limit should be lifted, but we can work around this for now. A user with a 75 TB filesystem reported the following journal replay error: https://github.com/koverstreet/bcachefs/issues/769 In journal replay we have to sort and dedup all the keys from the journal, which means we need a large contiguous allocation. Given that the user has 128GB of ram, the 2GB limit on allocation size has become far too small. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
kvmalloc() doesn't support allocations > INT_MAX, but vmalloc() does -
the limit should be lifted, but we can work around this for now.

A user with a 75 TB filesystem reported the following journal replay
error:
https://github.com/koverstreet/bcachefs/issues/769

In journal replay we have to sort and dedup all the keys from the
journal, which means we need a large contiguous allocation. Given that
the user has 128GB of ram, the 2GB limit on allocation size has become
far too small.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: darray: convert to alloc_hooks() 2024-09-09T13:41:49+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-08-22T07:50:22+00:00 a803fa551d53e4504a8dfca57817319f71030e2c better memory allocation profiling support Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
better memory allocation profiling support

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: darray: Don't pass NULL to memcpy() 2024-07-15T01:52:37+00:00 Tavian Barnes tavianator@tavianator.com 2024-06-21T20:29:32+00:00 2e118ba36d56acf78084518dfb7cb53b1d417da0 memcpy's second parameter must not be NULL, even if size is zero. Signed-off-by: Tavian Barnes <tavianator@tavianator.com> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
memcpy's second parameter must not be NULL, even if size is zero.

Signed-off-by: Tavian Barnes <tavianator@tavianator.com>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: DARRAY_PREALLOCATED() 2024-01-01T16:46:52+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-30T19:38:29+00:00 099dc5c29dff52c0c37abcaa6cc747a1ac8df5fe Add support to darray for preallocating some number of elements. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Add support to darray for preallocating some number of elements.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Switch darray to kvmalloc() 2024-01-01T16:46:52+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-17T00:44:48+00:00 a58a6a58f5ad55aa1f5c54598c44f1d9938c1793 We sometimes use darrays for quite large buffers - the btree write buffer in particular needs large buffers, since it must be sized to hold all the write buffer keys outstanding in the journal. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
We sometimes use darrays for quite large buffers - the btree write
buffer in particular needs large buffers, since it must be sized to hold
all the write buffer keys outstanding in the journal.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Factor out darray resize slowpath 2024-01-01T16:46:52+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-08T22:11:44+00:00 73ab9e03861c22ec6723b7b110d62ba60f37c164 Move the slowpath (actually growing the darray) to an out-of-line function; also, add some helpers for the upcoming btree write buffer rewrite. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Move the slowpath (actually growing the darray) to an out-of-line
function; also, add some helpers for the upcoming btree write buffer
rewrite.

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