From: Ming Lei Date: Fri, 26 Apr 2019 02:39:37 +0000 (+0800) Subject: block/028: check if T10 verification fails X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=09c0fe1bf86e7a3a23f6e26621ebbe964e7a2c58;p=users%2Fsagi%2Fblktests.git block/028: check if T10 verification fails When T10 verification fails, the error code of BLK_STS_PROTECTION may not be propagated to user space, see mpage_end_io(). So seems the only reliable way for detecting the failure is to check dmesg. Cc: Martin K . Petersen Signed-off-by: Ming Lei [Omar: use DMESG_FILTER] Signed-off-by: Omar Sandoval --- diff --git a/check b/check index a623892..69565de 100755 --- a/check +++ b/check @@ -147,6 +147,7 @@ _check_dmesg() { -e "INFO: suspicious RCU usage" \ -e "INFO: possible circular locking dependency detected" \ -e "general protection fault:" \ + -e "blktests failure" \ "${seqres}.dmesg" # shellcheck disable=SC2181 if [[ $? -eq 0 ]]; then diff --git a/tests/block/028 b/tests/block/028 index 7bee691..5140d94 100755 --- a/tests/block/028 +++ b/tests/block/028 @@ -9,6 +9,7 @@ . common/scsi_debug DESCRIPTION="do I/O on scsi_debug with DIF/DIX enabled" +DMESG_FILTER="sed -r 's/(guard tag error at sector|ref tag error at location)/blktests failure: \\1/'" requires() { _have_scsi_debug