befs: make consistent use of befs_error()

befs_error() is used in potential errors that could happen in befs to
provide informational log messages. befs_debug() is silent when
CONFIG_BEFS_DEBUG=no, and very verbose when switched on, which is why it is
used for general debugging but not for errors.

Fix a few cases where the befs debug utility usage isn't following the
expected pattern. To make sure we have consistent information in the logs.

Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index 307645f9e284..679f69df3817 100644
--- a/fs/befs/btree.c
+++ b/fs/befs/btree.c
@@ -301,7 +301,8 @@ befs_btree_find(struct super_block *sb, const befs_data_stream *ds,
         kfree(this_node);
 
         if (res != BEFS_BT_MATCH) {
-                befs_debug(sb, "<--- %s Key %s not found", __func__, key);
+                befs_error(sb, "<--- %s Key %s not found", __func__, key);
+                befs_debug(sb, "<--- %s ERROR", __func__);
                 *value = 0;
                 return BEFS_BT_NOT_FOUND;
         }
@@ -358,7 +359,8 @@ befs_find_key(struct super_block *sb, struct befs_btree_node *node,
 
         eq = befs_compare_strings(thiskey, keylen, findkey, findkey_len);
         if (eq < 0) {
-                befs_debug(sb, "<--- %s %s not found", __func__, findkey);
+                befs_error(sb, "<--- %s %s not found", __func__, findkey);
+                befs_debug(sb, "<--- %s ERROR", __func__);
                 return BEFS_BT_NOT_FOUND;
         }