From b7af0635c87ff78d6bd523298ab7471f9ffd3ce5 Mon Sep 17 00:00:00 2001 From: Filipe Manana Date: Wed, 30 Nov 2022 15:51:20 +0000 Subject: [PATCH] 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 Reviewed-by: Johannes Thumshirn Signed-off-by: Filipe Manana Reviewed-by: David Sterba Signed-off-by: David Sterba --- fs/btrfs/messages.h | 6 +++--- 1 file 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)); \ } \ } \ -- 2.11.0