mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: target-devel <target-devel@vger.kernel.org>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Roland Dreier <roland@kernel.org>,
	Or Gerlitz <ogerlitz@mellanox.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH/for-next 0/3] iscsi-target/iser-target: Fix breakage
Date: Thu, 25 Apr 2013 07:40:28 +0000	[thread overview]
Message-ID: <1366875631-18795-1-git-send-email-nab@linux-iscsi.org> (raw)

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

Hi folks,

This series addresses two bugs within v3.10 for-next code related to
the upcoming iscsi-target series adding multi-transport support, along
with a third iser-target bugfix related to early ISCSI_OP_SCSI_CMD
exception handling.

These three patches are being folded into for-next/for-next-merge code
now..

Thanks!

--nab

Nicholas Bellinger (3):
  iscsi-target: Fix solicited NopIN handling with RDMAExtentions=No
  iscsi-target: Fix iscsit_handle_scsi_cmd() exception se_cmd leak
  iser-target: Add special case for early ISCSI_OP_SCSI_CMD exception
    handling

 drivers/infiniband/ulp/isert/ib_isert.c |    7 ++++++
 drivers/target/iscsi/iscsi_target.c     |   32 ++++++++++++++++++------------
 2 files changed, 26 insertions(+), 13 deletions(-)

-- 
1.7.2.5


             reply	other threads:[~2013-04-25  7:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  7:40 Nicholas A. Bellinger [this message]
2013-04-25  7:40 ` [PATCH/for-next 1/3] iscsi-target: Fix solicited NopIN handling with RDMAExtentions=No Nicholas A. Bellinger
2013-04-25  7:40 ` [PATCH/for-next 2/3] iscsi-target: Fix iscsit_handle_scsi_cmd() exception se_cmd leak Nicholas A. Bellinger
2013-04-25  7:40 ` [PATCH/for-next 3/3] iser-target: Add special case for early ISCSI_OP_SCSI_CMD exception handling Nicholas A. Bellinger

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=1366875631-18795-1-git-send-email-nab@linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=roland@kernel.org \
    --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®