linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: target-devel <target-devel@vger.kernel.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH 0/2] target: Fix bugs when dealing with unconfigured devices
Date: Thu, 31 Jan 2013 23:19:13 +0000	[thread overview]
Message-ID: <1359674355-8590-1-git-send-email-nab@linux-iscsi.org> (raw)

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

Hi folks,

These two patches address two bugs that I've ran across when dealing with
backend devices that have failed to be successfully enabled, and remain
in an unconfigured state.

The first is a v3.8-rc1 specific regression due to fallout from the removal
of struct se_subsystem_dev, and the second is to avoid a possible divide by
zero when writing fabric_max_sectors when no block_size has been set by the
device.

The latter is being CC'ed to stable.

Thanks,

--nab

Nicholas Bellinger (2):
  target: Fix regression allowing unconfigured devices to fabric port
    link
  target: Fix divide by zero bug in fabric_max_sectors for unconfigured
    devices

 drivers/target/target_core_device.c          |    8 +++++++-
 drivers/target/target_core_fabric_configfs.c |    5 +++++
 2 files changed, 12 insertions(+), 1 deletions(-)

-- 
1.7.2.5


             reply	other threads:[~2013-01-31 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 23:19 Nicholas A. Bellinger [this message]
2013-01-31 23:19 ` [PATCH 1/2] target: Fix regression allowing unconfigured devices to fabric port link Nicholas A. Bellinger
2013-01-31 23:19 ` [PATCH 2/2] target: Fix divide by zero bug in fabric_max_sectors for unconfigured devices 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=1359674355-8590-1-git-send-email-nab@linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).