summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorMaurizio Lombardi <mlombard@redhat.com>2026-07-17 16:38:28 +0200
committerMartin K. Petersen (Oracle) <mkp@kernel.org>2026-08-28 22:18:58 -0400
commitd5869dae5080e976d4b03cc33eb7ceb527f242bf (patch)
tree018873380dde974fc3aa4ec4d368f19ba52d677a /scripts/Makefile.thinlto
parentc46cc9cee39bd6f395ab9ac98b1794705df13d7c (diff)
downloadlinux-d5869dae5080e976d4b03cc33eb7ceb527f242bf.tar.gz
linux-d5869dae5080e976d4b03cc33eb7ceb527f242bf.zip
scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands
When a LUN_RESET aborts a WRITE command that is in the TRANSPORT_WRITE_PENDING state, the target core sets CMD_T_ABORTED and waits for the frontend to finish processing. If the initiator subsequently sends the remaining dataout PDUs, __iscsit_check_dataout_hdr() catches the payload, stops the dataout timer if the sequence is final and finally dumps the data. However, the iSCSI target doesn't trigger the completion process for these aborted commands. Because of this, the abort path hangs indefinitely in target_put_cmd_and_wait(), leading to a deadlocked target worker thread. Fix this by explicitly calling target_complete_cmd() when the final dataout PDU is received for an aborted WRITE command. target_complete_cmd() detects the CMD_T_ABORTED flag and cleanly routes the command into target_abort_work, allowing the abort completion to successfully unblock. Signed-off-by: Maurizio Lombardi <mlombard@redhat.com> Reviewed-by: Laurence Oberman <loberman@redhat.com> Link: https://patch.msgid.link/20260717143828.76291-2-mlombard@redhat.com Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions