ext4: fix remaining two trace events to use same printk convention
authorRitesh Harjani <riteshh@linux.ibm.com>
Sat, 12 Mar 2022 05:39:55 +0000 (11:09 +0530)
committerTheodore Ts'o <tytso@mit.edu>
Tue, 15 Mar 2022 21:45:36 +0000 (17:45 -0400)
All ext4 & jbd2 trace events starts with "dev Major:Minor".
While we are still improving/adding the ftrace events for FC,
let's fix last two remaining trace events to follow the same
convention.

Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/8f33b163f0f29df2491c03b79f8ac96890ea5184.1647057583.git.riteshh@linux.ibm.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
include/trace/events/ext4.h

index aad97376e03257be08e449fd96ff8f51b01bcc75..ce2b3ad0ee86da3653046eeec1818d109c81b08b 100644 (file)
@@ -2654,7 +2654,7 @@ TRACE_EVENT(ext4_fc_replay_scan,
                __entry->off = off;
        ),
 
-       TP_printk("FC scan pass on dev %d,%d: error %d, off %d",
+       TP_printk("dev %d,%d error %d, off %d",
                  MAJOR(__entry->dev), MINOR(__entry->dev),
                  __entry->error, __entry->off)
 );
@@ -2680,7 +2680,7 @@ TRACE_EVENT(ext4_fc_replay,
                __entry->priv2 = priv2;
        ),
 
-       TP_printk("FC Replay %d,%d: tag %d, ino %d, data1 %d, data2 %d",
+       TP_printk("dev %d,%d: tag %d, ino %d, data1 %d, data2 %d",
                  MAJOR(__entry->dev), MINOR(__entry->dev),
                  __entry->tag, __entry->ino, __entry->priv1, __entry->priv2)
 );