Age | Commit message (Collapse) | Author |
|
|
|
Found with -fsanitize=leak
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
|
|
Also - add an option to bcachefs format for specifying it,
--superblock_size
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
|
|
|
|
writing for all devices
|
|
bitmap in fsck
|
|
read/write paths
|
|
down a heisenbug
|
|
during link
|
|
|
|
|
|
|
|
when RO
|
|
messages and options
|
|
flush_held_btree_writes()
|
|
improvements
|
|
|
|
|
|
|
|
|
|
bch2_bio_map()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
refactoring
|
|
|
|
|
|
when linking existing data, we weren't creating alloc btree keys - also,
we were calculating the wrong bucket...
|
|
interior btree nodes
|
|
|
|
|
|
|
|
|
|
|
|
This removes the implicit `-I libbcachefs` argument to $(CC), which in turn
requires a set of minor changes throughout the tools. There are two advantages
to this setup:
1) It is (arguably) easier to read, since the location of bcachefs includes
are easier to understand at a glance ("where does util.h live?")
2) It removes the need for a hack to include glibc's copy of
dirent.h explicitly via '/usr/include/dirent.h', because libbcachefs/
*also* has a dirent.h file and the compiler cannot disambiguate them.
This has some ramifications on systems where /usr/include may not
exist, such as NixOS.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Factor out bch2_pick_bucket_size() from the format code, and pick the
bucket size before picking the superblock location - that way we can
ensure the superblock gets its own bucket and doesn't trigger warnings
due to the allocation code noticing different types of data in the same
bucket.
|