Received-SPF: pass (google.com: domain of linux-kernel+bounces-40451-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Precedence: bulk
MIME-Version: 1.0
References: <cover.1701540918.git.lduncan@suse.com>
In-Reply-To: <cover.1701540918.git.lduncan@suse.com>
From: Lee Duncan <lduncan@suse.com>
Date: Fri, 26 Jan 2024 09:42:59 -0800
Message-ID: <CAPj3X_UWL8a3iXxA64bN5NDqWV2Try2-q84fYxaXk5uLCfGezQ@mail.gmail.com>
Subject: Re: [PATCH 0/2] scsi: target: iscsi: Fix two protocol issues
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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ping.

I believe I've addressed Chris' issues. Chris?

On Sat, Dec 2, 2023 at 10:45=E2=80=AFAM lduncan@suse.com <lduncan@suse.com>=
 wrote:
>
> 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
>