Mike Christie d19c4643a5 target: Fix ALUA transition state race between multiple initiators ... Multiple threads could be writing to alua_access_state at the same time, or there could be multiple STPGs in flight (different initiators sending them or one initiator sending them to different ports), or a combo of both and the core_alua_do_transition_tg_pt calls will race with each other. Because from the last patches we no longer delay running core_alua_do_transition_tg_pt_work, there does not seem to be any point in running that in a workqueue. And, we always wait for it to complete one way or another, so we can sleep in this code path. So, this patch made over target-pending just adds a mutex and does the work core_alua_do_transition_tg_pt_work was doing in core_alua_do_transition_tg_pt. There is also no need to use an atomic for the tg_pt_gp_alua_access_state. In core_alua_do_transition_tg_pt we will test and set it under the transition mutex. And, it is a int/32 bits so in the other places where it is read, we will never see it partially updated. Signed-off-by: Mike Christie <mchristi@redhat.com> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>		2017-03-30 23:12:40 -07:00
..
iscsi	target/iscsi: split iscsit_check_dataout_hdr()	2017-02-18 21:24:15 -08:00
target_core_backend.h	target: allow ALUA setup for some passthrough backends	2017-03-18 14:47:25 -07:00
target_core_base.h	target: Fix ALUA transition state race between multiple initiators	2017-03-30 23:12:40 -07:00
target_core_fabric.h	target: Inline transport_cmd_check_stop()	2017-02-09 00:39:14 -08:00