From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: target-devel@vger.kernel.org, bvanassche@acm.org, ddiss@suse.de,
michael.christie@oracle.com,
Sergey Samoylenko <s.samoylenko@yadro.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux@yadro.com, linux-scsi@vger.kernel.org
Subject: Re: [v3 0/2] scsi: target: fix sense key for invalid XCOPY request
Date: Tue, 24 Aug 2021 00:03:03 -0400 [thread overview]
Message-ID: <162977310550.31461.15478143015222238417.b4-ty@oracle.com> (raw)
In-Reply-To: <20210803145410.80147-1-s.samoylenko@yadro.com>
On Tue, 3 Aug 2021 17:54:08 +0300, Sergey Samoylenko wrote:
> 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:
>
> [...]
Applied to 5.15/scsi-queue, thanks!
[1/2] scsi: target: allows backend drivers to fail with specific sense codes
https://git.kernel.org/mkp/scsi/c/44678553ad7e
[2/2] scsi: target: fix sense key for invalid XCOPY request
https://git.kernel.org/mkp/scsi/c/0394b5048efd
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-08-24 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:54 [v3 0/2] scsi: target: fix sense key for invalid XCOPY request Sergey Samoylenko
2021-08-03 14:54 ` [v3 1/2] scsi: target: allows backend drivers to fail with specific sense codes Sergey Samoylenko
2021-08-03 14:54 ` [v3 2/2] scsi: target: fix sense key for invalid XCOPY request Sergey Samoylenko
2021-08-17 3:09 ` [v3 0/2] " Martin K. Petersen
2021-08-24 4:03 ` Martin K. Petersen [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=162977310550.31461.15478143015222238417.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=ddiss@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=michael.christie@oracle.com \
--cc=s.samoylenko@yadro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.