From: <lduncan@suse.com>
To: target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
dbond@suse.com, hare@suse.de, cleech@redhat.com,
michael.christie@oracle.com, Lee Duncan <lduncan@suse.com>
Subject: [PATCH 0/2] scsi: target: iscsi: Fix two protocol issues
Date: Thu, 7 Dec 2023 09:42:33 -0800 [thread overview]
Message-ID: <cover.1701540918.git.lduncan@suse.com> (raw)
From: Lee Duncan <lduncan@suse.com>
Recent boot testing using the fastlinq qedi iSCSI Converged Network
Adapter and an LIO target uncovered a couple of issues with the
kernel iSCSI target driver. The first patch addresses an issue
with the handling of iSCSI "immediate commands", which are allowed
but not common, and the second patch lowers the noise level of the
driver when initiators send PDUs with the read and/or write bits
set but no data, which is also allowed. (See RFC 3720)
Lee Duncan (2):
scsi: target: iscsi: handle SCSI immediate commands
scsi: target: iscsi: don't warn of R/W when no data
drivers/target/iscsi/iscsi_target.c | 17 ++++++-----------
drivers/target/iscsi/iscsi_target_util.c | 10 ++++++++--
2 files changed, 14 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-07 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 17:42 lduncan [this message]
2023-12-07 17:42 ` [PATCH 1/2] scsi: target: iscsi: handle SCSI immediate commands lduncan
2023-12-13 20:06 ` Chris Leech
2023-12-14 1:24 ` Lee Duncan
2023-12-14 20:29 ` Chris Leech
2024-01-17 21:09 ` Lee Duncan
2024-03-11 16:18 ` michael.christie
2023-12-07 17:42 ` [PATCH 2/2] scsi: target: iscsi: don't warn of R/W when no data lduncan
2024-03-09 18:05 ` Lee Duncan
2024-03-11 15:59 ` michael.christie
2024-01-26 17:42 ` [PATCH 0/2] scsi: target: iscsi: Fix two protocol issues Lee Duncan
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=cover.1701540918.git.lduncan@suse.com \
--to=lduncan@suse.com \
--cc=cleech@redhat.com \
--cc=dbond@suse.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).