bcachefs: Make sure allocation failure errors are logged
authorKent Overstreet <kent.overstreet@linux.dev>
Tue, 19 Dec 2023 23:08:19 +0000 (18:08 -0500)
committerKent Overstreet <kent.overstreet@linux.dev>
Mon, 1 Jan 2024 16:47:41 +0000 (11:47 -0500)
commita7dc10ce689a6224c1601d5d2e4ca57dd8cce9f6
treef3a43aebab1cfa79ff2d7636d08432aeff696f87
parent548673f8d39249d717d02038bd192a076e79edf0
bcachefs: Make sure allocation failure errors are logged

The previous patch fixed a bug in allocation path error handling, and it
would've been noticed sooner had it been logged properly.

Generally speaking, errors that shouldn't happen in normal operation and
are being returned up the stack should be logged: the write path was
already logging IO errors, but non IO errors were missed.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
fs/bcachefs/bcachefs.h
fs/bcachefs/btree_update_interior.c
fs/bcachefs/data_update.c
fs/bcachefs/io_misc.c
fs/bcachefs/io_write.c