Since util-linux version 2.40, dmesg supports "caller ID". When Linux
kernel supports CONFIG_PRINTK_CALLER, dmesg adds thread ID or CPU ID
with parenthesis such as [ T123] or [ C16] to each message. This
made the dmesg string check of the test case nvme/039 fail. Fix this by
filtering out the added caller ID field.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx>
---
tests/nvme/039 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/nvme/039 b/tests/nvme/039
index f92f852..a0f135c 100755
--- a/tests/nvme/039
+++ b/tests/nvme/039
@@ -24,7 +24,8 @@ last_dmesg()
{
local nr_lines=$1
- dmesg -t | grep -v "callbacks suppressed" | tail "-$nr_lines"
+ dmesg -t | grep -v "callbacks suppressed" | tail "-$nr_lines" \
+ | sed 's/\[.*\] //'
}
inject_unrec_read_on_read()
--
2.44.0
