target: Allow READ_CAPACITY opcode in ALUA Standby access state
authorNicholas Bellinger <nab@linux-iscsi.org>
Fri, 6 Jun 2014 06:37:00 +0000 (23:37 -0700)
committerNicholas Bellinger <nab@linux-iscsi.org>
Fri, 6 Jun 2014 08:21:12 +0000 (01:21 -0700)
commite7810c2d2c37fa8e58dda74b00790dab60fe6fba
treefe484bce9b8121904c2ae08f0eee246e757caca3
parent2363d196686e44c0158929e7cf96c8589a24a81b
target: Allow READ_CAPACITY opcode in ALUA Standby access state

This patch allows READ_CAPACITY + SAI_READ_CAPACITY_16 opcode
processing to occur while the associated ALUA group is in Standby
access state.

This is required to avoid host side LUN probe failures during the
initial scan if an ALUA group has already implicitly changed into
Standby access state.

This addresses a bug reported by Chris + Philip using dm-multipath
+ ESX hosts configured with ALUA multipath.

Reported-by: Chris Boot <crb@tiger-computing.co.uk>
Reported-by: Philip Gaw <pgaw@darktech.org.uk>
Cc: Chris Boot <crb@tiger-computing.co.uk>
Cc: Philip Gaw <pgaw@darktech.org.uk>
Cc: Hannes Reinecke <hare@suse.de>
Cc: stable@vger.kernel.org
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
drivers/target/target_core_alua.c