Re: [RESEND] [PATCH] Hold back_lock when calling iscsi_complete_task

On 2/25/19 2:02 AM, Johannes Thumshirn wrote: > On 22/02/2019 17:29, Lee Duncan wrote: >> From: Lee Duncan >> >> If there is an error queueing an iscsi command in >> iscsi_queuecommand(), for example if the transport fails >> to take the command in sessuin->tt->xmit_task(), then >> the error path

Re: [RESEND] [PATCH] Hold back_lock when calling iscsi_complete_task

On 22/02/2019 17:29, Lee Duncan wrote: > From: Lee Duncan > > If there is an error queueing an iscsi command in > iscsi_queuecommand(), for example if the transport fails > to take the command in sessuin->tt->xmit_task(), then > the error path can call iscsi_complete_task() without > first aquiri

[RESEND] [PATCH] Hold back_lock when calling iscsi_complete_task

From: Lee Duncan If there is an error queueing an iscsi command in iscsi_queuecommand(), for example if the transport fails to take the command in sessuin->tt->xmit_task(), then the error path can call iscsi_complete_task() without first aquiring the back_lock as required. This can lead to things