From: Sergey Samoylenko <s.samoylenko@yadro.com>
To: <martin.petersen@oracle.com>, <michael.christie@oracle.com>,
<ddiss@suse.de>, <bvanassche@acm.org>,
<target-devel@vger.kernel.org>
Cc: <linux-scsi@vger.kernel.org>, <linux@yadro.com>,
Sergey Samoylenko <s.samoylenko@yadro.com>
Subject: [v2 0/2] target: core: Fix sense key for invalid XCOPY request
Date: Mon, 26 Jul 2021 18:16:44 +0300 [thread overview]
Message-ID: <20210726151646.32631-1-s.samoylenko@yadro.com> (raw)
EXTENDED COPY tests in libiscsi [1] show that TCM doesn't
follow SPC4 when detects invalid parameters in a XCOPY
command or IO errors. The replies from TCM contain wrong sense
key or ASCQ for incorrect request.
The series fixes the following tests from libiscsi:
SCSI.ExtendedCopy.DescrType
SCSI.ExtendedCopy.DescrLimits
SCSI.ExtendedCopy.ParamHdr
SCSI.ExtendedCopy.ValidSegDescr
SCSI.ExtendedCopy.ValidTgtDescr
1. https://github.com/sahlberg/libiscsi
Sergey Samoylenko (2):
target: allows backend drivers to fail with specific sense codes
target: core: Fix sense key for invalid XCOPY request
drivers/target/target_core_transport.c | 21 ++++++++++++++++++---
drivers/target/target_core_xcopy.c | 26 +++++++++++++++-----------
include/target/target_core_backend.h | 1 +
include/target/target_core_base.h | 2 ++
4 files changed, 36 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-26 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 15:16 Sergey Samoylenko [this message]
2021-07-26 15:16 ` [v2 1/2] target: allows backend drivers to fail with specific sense codes Sergey Samoylenko
2021-07-30 16:37 ` David Disseldorp
2021-08-02 18:31 ` Sergey Samoylenko
2021-08-03 12:33 ` David Disseldorp
2021-07-26 15:16 ` [v2 2/2] target: core: Fix sense key for invalid XCOPY request Sergey Samoylenko
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=20210726151646.32631-1-s.samoylenko@yadro.com \
--to=s.samoylenko@yadro.com \
--cc=bvanassche@acm.org \
--cc=ddiss@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).