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)
committerJiri Slaby <jslaby@suse.cz>
Fri, 20 Jun 2014 15:34:16 +0000 (17:34 +0200)
commitbf8af413dcf4591bcc8f823133c4a2355c189458
tree6ee896dac099d0ca2770ced1f2695804f8236381
parenta51660781e72c3663e4e7f7a09b625a38c3d1f1a
target: Allow READ_CAPACITY opcode in ALUA Standby access state

commit e7810c2d2c37fa8e58dda74b00790dab60fe6fba upstream.

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.

(Drop v3.15 specific set_ascq usage - nab)

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>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
drivers/target/target_core_alua.c