summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/messages.h
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2022-11-30 16:51:20 +0100
committerDavid Sterba <dsterba@suse.com>2022-12-05 18:00:59 +0100
commitb7af0635c87ff78d6bd523298ab7471f9ffd3ce5 (patch)
tree36dc1a446ec1c1da15355052d4164221cfd3049a /fs/btrfs/messages.h
parentbtrfs: sync some cleanups from progs into uapi/btrfs.h (diff)
downloadlinux-b7af0635c87ff78d6bd523298ab7471f9ffd3ce5.tar.xz
linux-b7af0635c87ff78d6bd523298ab7471f9ffd3ce5.zip
btrfs: print transaction aborted messages with an error level
Currently we print the transaction aborted message with a debug level, but a transaction abort is an exceptional event that indicates something went wrong and it's useful to have it printed with an error level as it helps analysing problems in a production environment, where debug level messages are typically not logged. For example reports from syzbot never include the transaction aborted message, since the log level on the test machines is above the debug level. So change the log level from debug to error. Reviewed-by: Anand Jain <anand.jain@oracle.com> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/messages.h')
-rw-r--r--fs/btrfs/messages.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/fs/btrfs/messages.h b/fs/btrfs/messages.h
index 5ac410e313e4..190af1f698d9 100644
--- a/fs/btrfs/messages.h
+++ b/fs/btrfs/messages.h
@@ -197,13 +197,13 @@ do { \
&((trans)->fs_info->fs_state))) { \
first = true; \
if (WARN(abort_should_print_stack(errno), \
- KERN_DEBUG \
+ KERN_ERR \
"BTRFS: Transaction aborted (error %d)\n", \
(errno))) { \
/* Stack trace printed. */ \
} else { \
- btrfs_debug((trans)->fs_info, \
- "Transaction aborted (error %d)", \
+ btrfs_err((trans)->fs_info, \
+ "Transaction aborted (error %d)", \
(errno)); \
} \
} \