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:59:47 -0700 [thread overview]
Message-ID: <20190311225947.GF1315@vader> (raw)
In-Reply-To: <763669e2-7a87-6876-feae-49e82c5d4c8f@grimberg.me>
On Mon, Mar 11, 2019@03:58:02PM -0700, Sagi Grimberg wrote:
>
> > 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?
>
> Fine by me, you can fold it in..
Done and pushed.
prev parent reply other threads:[~2019-03-11 22:59 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
2019-03-11 22:58 ` Sagi Grimberg
2019-03-11 22:59 ` Omar Sandoval [this message]
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=20190311225947.GF1315@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