<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/bcachefs/Makefile, branch linux-6.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-04-03T18:44:18Z</updated>
<entry>
<title>bcachefs: Repair pass for scanning for btree nodes</title>
<updated>2024-04-03T18:44:18Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2024-03-12T03:11:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4409b8081d1624af814a9cda781ad9cdda3973cb'/>
<id>urn:sha1:4409b8081d1624af814a9cda781ad9cdda3973cb</id>
<content type='text'>
If a btree root or interior btree node goes bad, we're going to lose a
lot of data, unless we can recover the nodes that it pointed to by
scanning.

Fortunately btree node headers are fully self describing, and
additionally the magic number is xored with the filesytem UUID, so we
can do so safely.

This implements the scanning - next patch will rework topology repair to
make use of the found nodes.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: Etyzinger cleanups</title>
<updated>2024-04-03T18:44:18Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2024-03-22T23:26:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ca1e02f7e9a1352b3f7b04de821ae74c9e07df74'/>
<id>urn:sha1:ca1e02f7e9a1352b3f7b04de821ae74c9e07df74</id>
<content type='text'>
Pull out eytzinger.c and kill eytzinger_cmp_fn. We now provide
eytzinger0_sort and eytzinger0_sort_r, which use the standard cmp_func_t
and cmp_r_func_t callbacks.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: Split out recovery_passes.c</title>
<updated>2024-04-01T00:36:11Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2024-03-24T00:07:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d2554263adcb4041f3608cb7476f102fda036ccc'/>
<id>urn:sha1:d2554263adcb4041f3608cb7476f102fda036ccc</id>
<content type='text'>
We've grown a fair amount of code for managing recovery passes; tracking
which ones we're running, which ones need to be run, and flagging in the
superblock which ones need to be run on the next recovery.

So it's worth splitting out into its own file, this code is pretty
different from the code in recovery.c.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: pull out time_stats.[ch]</title>
<updated>2024-03-14T01:30:35Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2024-03-14T00:16:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f1ca1abfb0275db241363743ed3606b25b2b1a5c'/>
<id>urn:sha1:f1ca1abfb0275db241363743ed3606b25b2b1a5c</id>
<content type='text'>
prep work for lifting out of fs/bcachefs/

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: Silence gcc warnings about arm arch ABI drift</title>
<updated>2024-03-14T01:22:25Z</updated>
<author>
<name>Calvin Owens</name>
</author>
<published>2024-02-19T07:36:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c7cad231e83606a3ad627d5c4503272435c962a4'/>
<id>urn:sha1:c7cad231e83606a3ad627d5c4503272435c962a4</id>
<content type='text'>
32-bit arm builds emit a lot of spam like this:

    fs/bcachefs/backpointers.c: In function ‘extent_matches_bp’:
    fs/bcachefs/backpointers.c:15:13: note: parameter passing for argument of type ‘struct bch_backpointer’ changed in GCC 9.1

Apply the change from commit ebcc5928c5d9 ("arm64: Silence gcc warnings
about arch ABI drift") to fs/bcachefs/ to silence them.

Signed-off-by: Calvin Owens &lt;jcalvinowens@gmail.com&gt;
Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: counters.c -&gt; sb-counters.c</title>
<updated>2024-01-21T18:27:10Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2024-01-21T04:46:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3a58dfbc46c277b090f1b72c949e15da7e1290bf'/>
<id>urn:sha1:3a58dfbc46c277b090f1b72c949e15da7e1290bf</id>
<content type='text'>
Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: factor out thread_with_file, thread_with_stdio</title>
<updated>2024-01-06T04:24:19Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2023-12-31T15:04:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=96f37eabe7a5cb4746f369e959f935be464950be'/>
<id>urn:sha1:96f37eabe7a5cb4746f369e959f935be464950be</id>
<content type='text'>
thread_with_stdio now knows how to handle input - fsck can now prompt to
fix errors.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: bch_sb_field_downgrade</title>
<updated>2024-01-01T16:47:07Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2023-12-29T20:25:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84f1638795da1ff2084597de4251e9054f1ad728'/>
<id>urn:sha1:84f1638795da1ff2084597de4251e9054f1ad728</id>
<content type='text'>
Add a new superblock section that contains a list of
  { minor version, recovery passes, errors_to_fix }

that is - a list of recovery passes that must be run when downgrading
past a given version, and a list of errors to silently fix.

The upcoming disk accounting rewrite is not going to be fully
compatible: we're going to have to regenerate accounting both when
upgrading to the new version, and also from downgrading from the new
version, since the new method of doing disk space accounting is a
completely different architecture based on deltas, and synchronizing
them for every jounal entry write to maintain compatibility is going to
be too expensive and impractical.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: Factor out darray resize slowpath</title>
<updated>2024-01-01T16:46:52Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2023-11-08T22:11:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=73ab9e03861c22ec6723b7b110d62ba60f37c164'/>
<id>urn:sha1:73ab9e03861c22ec6723b7b110d62ba60f37c164</id>
<content type='text'>
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 &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
<entry>
<title>bcachefs: bch_sb_field_errors</title>
<updated>2023-11-02T01:11:08Z</updated>
<author>
<name>Kent Overstreet</name>
</author>
<published>2023-10-25T19:51:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5d26fa31ed2e260589f0bc8af010bb742f1231e'/>
<id>urn:sha1:f5d26fa31ed2e260589f0bc8af010bb742f1231e</id>
<content type='text'>
Add a new superblock section to keep counts of errors seen since
filesystem creation: we'll be addingcounters for every distinct fsck
error.

The new superblock section has entries of the for [ id, count,
time_of_last_error ]; this is intended to let us see what errors are
occuring - and getting fixed - via show-super output.

Signed-off-by: Kent Overstreet &lt;kent.overstreet@linux.dev&gt;
</content>
</entry>
</feed>
