From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Spencer Baugh <sbaugh@catern.com>
Cc: "open list:TARGET SUBSYSTEM" <linux-scsi@vger.kernel.org>,
"open list:TARGET SUBSYSTEM" <target-devel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Joern Engel <joern@purestorage.com>,
Spencer Baugh <Spencer.baugh@purestorage.com>,
Roland Dreier <roland@purestorage.com>
Subject: Re: [PATCH] target: Fix handling of small allocation lengths in REPORT LUNS
Date: Thu, 13 Aug 2015 16:23:04 -0700 [thread overview]
Message-ID: <1439508184.31978.57.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <1439445958-24753-1-git-send-email-sbaugh@catern.com>
Hi Spencer & Co,
On Wed, 2015-08-12 at 23:05 -0700, Spencer Baugh wrote:
> From: Roland Dreier <roland@purestorage.com>
>
> REPORT LUNS should not fail just because the allocation length is less
> than 16. The relevant section of SPC-4 is:
>
> 4.2.5.6 Allocation length
>
> The ALLOCATION LENGTH field specifies the maximum number of bytes or
> blocks that an application client has allocated in the Data-In
> Buffer. The ALLOCATION LENGTH field specifies bytes unless a
> different requirement is stated in the command definition.
>
> An allocation length of zero specifies that no data shall be
> transferred. This condition shall not be considered an error.
>
> So we should just truncate our response rather than return an error.
>
> Signed-off-by: Roland Dreier <roland@purestorage.com>
> Signed-off-by: Spencer Baugh <sbaugh@catern.com>
This patch looks fine, but it currently doesn't apply to
target-pending/master code due Roland's earlier patch:
target: REPORT LUNS should return LUN 0 even for dynamic ACLs
https://git.kernel.org/cgit/linux/kernel/git/nab/target-pending.git/commit/?id=9c395170a559d3b23dad100b01fc4a89d661c698
Would you be so kind to respin atop current target-pending/master..?
Thank you,
--nab
next prev parent reply other threads:[~2015-08-13 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 6:05 Spencer Baugh
2015-08-13 23:23 ` Nicholas A. Bellinger [this message]
2015-08-14 4:59 ` [PATCH v2] " Spencer Baugh
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=1439508184.31978.57.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=Spencer.baugh@purestorage.com \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roland@purestorage.com \
--cc=sbaugh@catern.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
all inboxes | Powered by JetHome®