From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH v2] nvme: test out-of-range I/O access (file backend)
Date: Mon, 11 Mar 2019 15:49:04 -0700 [thread overview]
Message-ID: <20190311224904.GE1315@vader> (raw)
In-Reply-To: <20190311221855.27375-1-sagi@grimberg.me>
On Mon, Mar 11, 2019@03:18:55PM -0700, Sagi Grimberg wrote:
> Test that we correctly fail an out-of-range access
> with a proper NVMe status code.
>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
> Changes from v1:
> - "ERROR:" prefix to err message
> - document that we are testing file backend
Ah, so this fails for me because I have nvme-cli 1.7 which is missing
your 9c891c139894 ("nvmet: check fileio lba range access boundaries").
How about we just look at the exit code of nvme read instead of relying
on that output?
diff --git a/tests/nvme/018 b/tests/nvme/018
index 30140ae..b09c29c 100755
--- a/tests/nvme/018
+++ b/tests/nvme/018
@@ -2,7 +2,8 @@
# SPDX-License-Identifier: GPL-3.0+
# Copyright (C) 2018 Sagi Grimberg
#
-# Test NVMe out of range access on a file backend
+# Test NVMe out of range access on a file backend. Regression test for commit
+# 9c891c139894 ("nvmet: check fileio lba range access boundaries").
. tests/nvme/rc
@@ -38,11 +39,12 @@ test() {
cat "/sys/block/${nvmedev}n1/uuid"
cat "/sys/block/${nvmedev}n1/wwid"
- sectors=$(blockdev --getsz /dev/${nvmedev}n1)
- bs=$(blockdev --getbsz /dev/${nvmedev}n1)
+ local sectors
+ local bs
+ sectors="$(blockdev --getsz "/dev/${nvmedev}n1")"
+ bs="$(blockdev --getbsz "/dev/${nvmedev}n1")"
- nvme read "/dev/${nvmedev}n1" -s $sectors -c 0 -z $bs
- if [[ ! $? ]]; then
+ if nvme read "/dev/${nvmedev}n1" -s "$sectors" -c 0 -z "$bs"; then
echo "ERROR: Successfully read out of device lba range"
fi
diff --git a/tests/nvme/018.out b/tests/nvme/018.out
old mode 100755
new mode 100644
index 0ab3b2a..68a0194
--- a/tests/nvme/018.out
+++ b/tests/nvme/018.out
@@ -1,6 +1,5 @@
Running nvme/018
91fdba0d-f87b-4c25-b80f-db7be1418b9e
uuid.91fdba0d-f87b-4c25-b80f-db7be1418b9e
-read:CAP_EXCEEDED: The execution of the command has caused the capacity of the namespace to be exceeded(6081)
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test complete
next prev parent reply other threads:[~2019-03-11 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 22:18 [PATCH v2] nvme: test out-of-range I/O access (file backend) Sagi Grimberg
2019-03-11 22:49 ` Omar Sandoval [this message]
2019-03-11 22:58 ` Sagi Grimberg
2019-03-11 22:59 ` Omar Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190311224904.GE1315@vader \
--to=osandov@osandov.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.