linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Samoylenko <s.samoylenko@yadro.com>
To: <martin.petersen@oracle.com>, <michael.christie@oracle.com>,
	<target-devel@vger.kernel.org>
Cc: <linux-scsi@vger.kernel.org>, <linux@yadro.com>,
	Sergey Samoylenko <s.samoylenko@yadro.com>
Subject: [PATCH 0/1] scsi: target: core: Fix sense key for invalid XCOPY request
Date: Thu, 24 Jun 2021 14:19:25 +0300	[thread overview]
Message-ID: <20210624111926.63176-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 (1):
  scsi: target: core: Fix sense key for invalid XCOPY request

 drivers/target/target_core_xcopy.c | 26 +++++++++++++++-----------
 1 file changed, 15 insertions(+), 11 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-06-24 11:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 11:19 Sergey Samoylenko [this message]
2021-06-24 11:19 ` [PATCH 1/1] scsi: target: core: Fix sense key for invalid XCOPY request Sergey Samoylenko
2021-06-24 15:49   ` kernel test robot
2021-06-24 15:57   ` Bart Van Assche
2021-06-24 17:27     ` Sergey Samoylenko
2021-07-21 21:45 ` [PATCH 0/1] " David Disseldorp
2021-07-22 11:03   ` Sergey Samoylenko
2021-07-22 13:27     ` David Disseldorp

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=20210624111926.63176-1-s.samoylenko@yadro.com \
    --to=s.samoylenko@yadro.com \
    --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).