linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@daterainc.com>
To: target-devel <target-devel@vger.kernel.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Thomas Glanzmann <thomas@glanzmann.de>,
	Douglas Gilbert <dgilbert@interlog.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH 0/3] target: EXTENDED_COPY bugfixes for v3.12-rc
Date: Tue,  8 Oct 2013 19:56:30 +0000	[thread overview]
Message-ID: <1381262193-19797-1-git-send-email-nab@daterainc.com> (raw)

From: Nicholas Bellinger <nab@linux-iscsi.org>

Hi folks,

Here are a few extra EXTENDED_COPY bugfixes that have come up recently.

This includes:

  - Reporting the correct ASC/ASCQ during target_do_xcopy() failures
  - Allow non zero list IDs to be processed as SNLID=1
  - Reject copy offload requests on source + destination devices when
    device attribute emulate_3pc has been explicitly disabled.

Thanks again to Thomas + Doug for their testing + feedback!

--nab

Nicholas Bellinger (3):
  target: Make target_do_xcopy failures return INVALID_PARAMETER_LIST
  target: Allow non zero ListID in EXTENDED_COPY parameter list
  target: Reject EXTENDED_COPY when emulate_3pc is disabled

 drivers/target/target_core_xcopy.c |   33 ++++++++++++++++++++-------------
 1 file changed, 20 insertions(+), 13 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2013-10-08 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 19:56 Nicholas A. Bellinger [this message]
2013-10-08 19:56 ` [PATCH 1/3] target: Make target_do_xcopy failures return INVALID_PARAMETER_LIST Nicholas A. Bellinger
2013-10-08 19:56 ` [PATCH 2/3] target: Allow non zero ListID in EXTENDED_COPY parameter list Nicholas A. Bellinger
2013-10-08 19:56 ` [PATCH 3/3] target: Reject EXTENDED_COPY when emulate_3pc is disabled Nicholas A. Bellinger
2013-10-08 20:20 ` [PATCH 0/3] target: EXTENDED_COPY bugfixes for v3.12-rc Thomas Glanzmann

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=1381262193-19797-1-git-send-email-nab@daterainc.com \
    --to=nab@daterainc.com \
    --cc=dgilbert@interlog.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=target-devel@vger.kernel.org \
    --cc=thomas@glanzmann.de \
    /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 NNTP newsgroup(s).