From: Jens Axboe <[email protected]>
To: Kanchan Joshi <[email protected]>
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCH liburing] test/io_uring_passthrough: add test case for submission failure
Date: Tue, 23 Aug 2022 09:47:53 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 8/23/22 9:27 AM, Kanchan Joshi wrote:
> Increase the coverage by adding a test which triggers submission-failure
> from nvme side.
> Issue an ill-formed passthrough command by populating invalid nsid
> value. If cqe->res is zero, report failure of the test.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2022-08-23 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220823153811epcas5p3e9262beb5b6dc0ae58f4bcf7486473de@epcas5p3.samsung.com>
2022-08-23 15:27 ` [PATCH liburing] test/io_uring_passthrough: add test case for submission failure Kanchan Joshi
2022-08-23 15:47 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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