From: Hannes Reinecke <hare@suse.de>
To: Nic Bellinger <nab@daterainc.com>
Cc: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Ewan Milne <emilne@redhat.com>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/8] tcm_loop updates
Date: Thu, 18 Jun 2015 11:43:34 +0200 [thread overview]
Message-ID: <1434620622-65391-1-git-send-email-hare@suse.de> (raw)
Hi Nic,
As tcm_loop claims to be a SAS HBA I thought it a good idea to
hook it into the SAS transport class, so that we have the entire
(virtual) SAS topology in sysfs now.
And even lsscsi is happy:
# lsscsi -H -t
[10] tcm_loopback sas:0x6001405cc9332c5a
# lsscsi -t
[10:0:0:0] disk sas:0x6001405e41925ad3 /dev/sdf
[10:0:1:0] disk sas:0x6001405e41925ad3 /dev/sdg
I've also included some pending fixes / updates I did for
LIO target, mostly done to reproduce issues I've been facing:
- Disallow READ CAPACITY in standby
This is a long-standing issue with the linux SCSI stack and
multipathing, both assuming that READ CAPACITY will always
succeed. With that patch we can finally debug and fix this.
- Export the 'write_protect' attribute for demo-mode LUNs
- Some more UAs to be issued
As usual, reviews and comments are welcome.
Hannes Reinecke (8):
tcm_loop: Hook into SAS transport class
tcm_loop: Add SAS transport topology
tcm_loop: Remove SAS vestigies
tcm_loop: Send I_T_NEXUS_LOSS_OCCURRED UA
tcm_loop: Rescan SCSI target on transport online
target: Issue Power-On/Reset UA upon LUN instantiation
target_core_alua: disallow READ_CAPACITY when in standby
target: display 'write_protect' attribute for demo-mode LUNs
drivers/target/loopback/tcm_loop.c | 186 +++++++++++++++++++++++----
drivers/target/loopback/tcm_loop.h | 3 +
drivers/target/target_core_alua.c | 9 --
drivers/target/target_core_device.c | 43 ++++++-
drivers/target/target_core_fabric_configfs.c | 42 ++++++
drivers/target/target_core_internal.h | 1 +
drivers/target/target_core_tpg.c | 17 +++
include/target/target_core_fabric.h | 1 +
8 files changed, 261 insertions(+), 41 deletions(-)
--
1.8.5.2
next reply other threads:[~2015-06-18 9:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 9:43 Hannes Reinecke [this message]
2015-06-18 9:43 ` [PATCH 1/8] tcm_loop: Hook into SAS transport class Hannes Reinecke
2015-06-18 9:43 ` [PATCH 2/8] tcm_loop: Add SAS transport topology Hannes Reinecke
2015-06-18 9:43 ` [PATCH 3/8] tcm_loop: Remove SAS vestigies Hannes Reinecke
2015-06-18 9:43 ` [PATCH 4/8] tcm_loop: Send I_T_NEXUS_LOSS_OCCURRED UA Hannes Reinecke
2015-06-18 9:43 ` [PATCH 5/8] tcm_loop: Rescan SCSI target on transport online Hannes Reinecke
2015-06-18 9:43 ` [PATCH 6/8] target: Issue Power-On/Reset UA upon LUN instantiation Hannes Reinecke
2015-06-18 9:43 ` [PATCH 7/8] target_core_alua: disallow READ_CAPACITY when in standby Hannes Reinecke
2015-06-18 11:40 ` Chris Boot
2015-06-18 14:32 ` Hannes Reinecke
2015-06-19 6:49 ` Christoph Hellwig
2015-06-19 7:07 ` Hannes Reinecke
2015-06-18 9:43 ` [PATCH 8/8] target: display 'write_protect' attribute for demo-mode LUNs Hannes Reinecke
2015-06-19 6:51 ` Christoph Hellwig
2015-06-19 7:05 ` Hannes Reinecke
2015-06-19 6:48 ` [PATCH 0/8] tcm_loop updates Christoph Hellwig
2015-06-19 7:13 ` Hannes Reinecke
2015-06-23 8:29 ` Nicholas A. Bellinger
2015-06-23 9:05 ` Hannes Reinecke
2015-07-07 0:25 ` Nicholas A. Bellinger
2015-07-07 5:50 ` Hannes Reinecke
2015-07-07 6:26 ` Nicholas A. Bellinger
2015-07-07 6:29 ` Hannes Reinecke
2015-07-07 6:42 ` 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=1434620622-65391-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@daterainc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.