On 12/08/2015 01:48 AM, Himanshu Madhani wrote: > From: Alexei Potashnik <alexei@xxxxxxxxxxxxxxx> > > Until now ack'ing of a new PLOGI has only been delayed if there > was an existing session for the same WWN. Ack was released when > the session deletion completed. > > If there was another WWN session with the same fc_id/loop_id pair > (aka "conflicting session"), PLOGI was still ack'ed immediately. > This potentially caused a problem when old session deletion logged > fc_id/loop_id out of FW after new session has been established. > > Two work-arounds were attempted before: > 1. Dropping PLOGIs until conflicting session goes away. > 2. Detecting initiator being logged out of FW and issuing LOGO > to force re-login. > > This patch introduces proper solution to the problem where PLOGI > is held until either existing session with same WWN or any > conflicting session goes away. Mechanism supports one session holding > two PLOGI acks as well as one PLOGI ack being held by many sessions. > > Signed-off-by: Alexei Potashnik <alexei@xxxxxxxxxxxxxxx> > Acked-by: Quinn Tran <quinn.tran@xxxxxxxxxx> > Signed-off-by: Himanshu Madhani <himanshu.madhani@xxxxxxxxxx> > --- Reviewed-by: Hannes Reinecke <hare@xxxxxxxx> Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@xxxxxxx +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
