From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH 2/2 blktests] nvme: test out-of-range I/O access
Date: Mon, 11 Mar 2019 13:35:23 -0700 [thread overview]
Message-ID: <20190311203523.GA1315@vader> (raw)
In-Reply-To: <20190306094643.10262-2-sagi@grimberg.me>
On Wed, Mar 06, 2019@01:46:43AM -0800, 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>
> ---
> tests/nvme/018 | 58 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/nvme/018.out | 6 +++++
> 2 files changed, 64 insertions(+)
> create mode 100755 tests/nvme/018
> create mode 100755 tests/nvme/018.out
>
> diff --git a/tests/nvme/018 b/tests/nvme/018
> new file mode 100755
> index 000000000000..939573263c87
> --- /dev/null
> +++ b/tests/nvme/018
> @@ -0,0 +1,58 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-3.0+
> +# Copyright (C) 2018 Sagi Grimberg
> +#
> +# Test NVMe out of range access.
Is this a test for a specific kernel commit? It fails on 5.0.
next prev parent reply other threads:[~2019-03-11 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 9:46 [PATCH 1/2 blktests] nvme: add udevadm settle before disconnecting Sagi Grimberg
2019-03-06 9:46 ` [PATCH 2/2 blktests] nvme: test out-of-range I/O access Sagi Grimberg
2019-03-06 20:08 ` Chaitanya Kulkarni
2019-03-06 20:28 ` Sagi Grimberg
2019-03-06 20:31 ` Chaitanya Kulkarni
2019-03-07 7:45 ` Johannes Thumshirn
2019-03-11 20:35 ` Omar Sandoval [this message]
2019-03-11 22:14 ` Sagi Grimberg
2019-03-11 22:21 ` Omar Sandoval
2019-03-11 22:28 ` Sagi Grimberg
2019-03-06 19:53 ` [PATCH 1/2 blktests] nvme: add udevadm settle before disconnecting Chaitanya Kulkarni
2019-03-11 20:36 ` 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=20190311203523.GA1315@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox