[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1499789824.2586.16.camel@wdc.com>
Date: Tue, 11 Jul 2017 16:17:05 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: Bart Van Assche <Bart.VanAssche@....com>,
"nab@...ux-iscsi.org" <nab@...ux-iscsi.org>
CC: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mchristi@...hat.com" <mchristi@...hat.com>,
"roland@...estorage.com" <roland@...estorage.com>,
"target-devel@...r.kernel.org" <target-devel@...r.kernel.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"hare@...e.de" <hare@...e.de>
Subject: Re: [PATCH] iscsi-target: Reject immediate data underflow larger than
SCSI transfer length
On Tue, 2017-07-11 at 00:22 -0700, Nicholas A. Bellinger wrote:
> So rejecting this case as already done in commit abb85a9b51 is the
> correct approach for >= v4.3.y.
Hello Nic,
I hope that you agree that the current target_cmd_size_check() implementation
is complicated and ugly. Patch 30/33 of the patch series I referred to in my
e-mail removes a significant number of lines of code from that function. So
my patch series not only makes target_cmd_size_check() easier to maintain and
to verify but it makes that function also faster. Hence please reconsider the
approach from my patch series. For patch 30/33, see also
https://www.spinics.net/lists/target-devel/msg15384.html.
Bart.
Powered by blists - more mailing lists