linux.git/fs/bcachefs/io_write.c, branch v6.9 Linux kernel source tree bcachefs: Initialize bch_write_op->failed in inline data path 2024-05-06T14:58:17+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-05-04T16:29:46+00:00 1267df40acb2da62b1641abae26132411d093fb3 Normally this is initialized in __bch2_write(), which is executed in a loop, but the inline data path skips this. Reported-by: syzbot+fd3ccb331eb21f05d13b@syzkaller.appspotmail.com Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Normally this is initialized in __bch2_write(), which is executed in a
loop, but the inline data path skips this.

Reported-by: syzbot+fd3ccb331eb21f05d13b@syzkaller.appspotmail.com
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Inodes need extra padding for varint_decode_fast() 2024-05-06T14:58:17+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-05-03T15:31:22+00:00 4a8521b6bb81abba9d80d60b80908c77c9236ced Reported-by: syzbot+66b9b74f6520068596a9@syzkaller.appspotmail.com Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Reported-by: syzbot+66b9b74f6520068596a9@syzkaller.appspotmail.com
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: time_stats: split stats-with-quantiles into a separate structure 2024-03-14T01:38:01+00:00 Darrick J. Wong djwong@kernel.org 2024-02-01T20:41:42+00:00 273960b8f374b95ebd234a99607b7887f515c791 Currently, struct time_stats has the optional ability to quantize the information that it collects. This is /probably/ useful for callers who want to see quantized information, but it more than doubles the size of the structure from 224 bytes to 464. For users who don't care about that (e.g. upcoming xfs patches) and want to avoid wasting 240 bytes per counter, split the two into separate pieces. Signed-off-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Currently, struct time_stats has the optional ability to quantize the
information that it collects.  This is /probably/ useful for callers who
want to see quantized information, but it more than doubles the size of
the structure from 224 bytes to 464.  For users who don't care about
that (e.g. upcoming xfs patches) and want to avoid wasting 240 bytes per
counter, split the two into separate pieces.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: more informative write path error message 2024-03-14T01:22:25+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-02-17T01:03:12+00:00 3235e04afef8b4ad72d92f05f8f33f6552793223 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Clamp replicas_required to replicas 2024-02-14T01:33:38+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-02-11T02:01:40+00:00 4e07447503f01766ae976207eb3b947437ed8dbc This prevents going emergency read only when the user has specified replicas_required > replicas. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
This prevents going emergency read only when the user has specified
replicas_required > replicas.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: opts->compression can now also be applied in the background 2024-01-21T18:27:10+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-16T21:20:21+00:00 d7e77f53e90e1eb87838eed7c651531427b9114a The "apply this compression method in the background" paths now use the compression option if background_compression is not set; this means that setting or changing the compression option will cause existing data to be compressed accordingly in the background. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
The "apply this compression method in the background" paths now use the
compression option if background_compression is not set; this means that
setting or changing the compression option will cause existing data to
be compressed accordingly in the background.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Don't log errors if BCH_WRITE_ALLOC_NOWAIT 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-11T04:08:30+00:00 4ecad0da9de830681ffff973bc0d47b07612bbe6 Previously, we added logging in the write path to ensure that any unexpected errors getting reported to userspace have a log message; but BCH_WRITE_ALLOC_NOWAIT is a special case, it's used for promotes where errors are expected and not reported out to userspace - so we need to silence those. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Previously, we added logging in the write path to ensure that any
unexpected errors getting reported to userspace have a log message; but
BCH_WRITE_ALLOC_NOWAIT is a special case, it's used for promotes where
errors are expected and not reported out to userspace - so we need to
silence those.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: for_each_keylist_key() declares loop iter 2024-01-01T16:47:43+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-22T03:24:46+00:00 1a2a9f9f53a6c4d77bc16062fcb65c7169fb6ed1 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: bkey_for_each_ptr() now declares loop iter 2024-01-01T16:47:43+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-21T20:47:15+00:00 0beebd92457c3221b59840487591c1dff8071168 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: for_each_btree_key() now declares loop iter 2024-01-01T16:47:42+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-17T03:30:09+00:00 80eab7a7c2808f84e56ba1f2f1408a16c46d3bdc Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>