* [PATCH v2] scsi: target: Fix NULL se_tpg dereference in target_complete()
@ 2026-07-25 16:58 Yehyeong Lee
2026-07-25 20:44 ` Mike Christie
0 siblings, 1 reply; 3+ messages in thread
From: Yehyeong Lee @ 2026-07-25 16:58 UTC (permalink / raw)
To: martin.petersen, michael.christie
Cc: ddiss, linux-scsi, target-devel, linux-kernel, Yehyeong Lee, stable
Commit a47fa41381a0 ("scsi: target: Fix NULL dereference on XCOPY
completion") guarded target_complete() against a NULL se_tpg_wwn, which the
EXTENDED COPY worker hits because its global xcopy_pt_tpg carries no
se_tpg_wwn. target_complete() dereferences
cmd->se_sess->se_tpg->se_tpg_wwn; that fix handled the innermost pointer.
The same statement can fault one level earlier: se_sess->se_tpg itself may
be NULL. After a session is deregistered, transport_deregister_session()
clears se_sess->se_tpg, yet the isert receive path can still submit and
complete a command that references that session, so the backend completion
runs target_complete() with se_tpg == NULL and dereferences it:
Oops: general protection fault, probably for non-canonical address ...
KASAN: null-ptr-deref in range [0x0000000000000080-0x0000000000000087]
Workqueue: ib-comp-wq ib_cq_poll_work
RIP: 0010:target_complete_cmd_with_sense.part.0+0x17d/0xc90
Call Trace:
fd_execute_rw
__target_execute_cmd
iscsit_execute_cmd
iscsit_sequence_cmd
isert_recv_done
__ib_process_cq
ib_cq_poll_work
The exact window in which an isert completion outlives the session
deregistration has not been pinned down; the guard defends the dereference
regardless of how the command reaches this point.
Load se_tpg first and fall back to a NULL wwn when it is absent. The
read is lockless - transport_deregister_session() clears the field under
se_tpg->session_lock, which target_complete() does not hold - so use
READ_ONCE() to keep the compiler from re-fetching se_sess->se_tpg after
the NULL test. The existing "if (!wwn)" path already queues the
completion on cmd->cpuid, so no new branch is needed; this extends that
guard by one pointer.
target_submit() reads the same chain (se_sess->se_tpg->se_tpg_tfo) and is
exposed to the identical NULL. That path has not been reproduced here and
is left for a separate change.
Reproduced with soft-RoCE (rdma_rxe) and KASAN under iSCSI connection
churn; no kernel-side test hooks were needed.
Fixes: 39ae3edda325 ("scsi: target: core: Make completion affinity configurable")
Cc: stable@vger.kernel.org
Signed-off-by: Yehyeong Lee <yhlee@isslab.korea.ac.kr>
---
v2:
- Use READ_ONCE() for the lockless read of se_sess->se_tpg. The field is
cleared concurrently by transport_deregister_session(), so nothing
prevents the compiler from re-fetching it after the NULL test. The
store side is a plain aligned pointer write under se_tpg->session_lock
and is left unannotated; happy to add WRITE_ONCE() there as well if
preferred.
- Retested from scratch; every number below is from the v2 build.
Tested on 7.2.0-rc4 with soft-RoCE (rdma_rxe) + KASAN under iSCSI/iSER
connection churn. Unpatched, 5 of 10 runs oops with the same RIP
(target_complete_cmd_with_sense.part.0+0x17d). With this patch, 20
consecutive runs show no oops.
To confirm that the guard - and not an incidental timing change - is what
prevents the crash, a build carrying an additional print inside the new
NULL branch was run 10 more times: a NULL se_tpg was observed 9 times
across 7 of those runs and was handled every time, with no oops.
Some runs end early with an initiator-side login timeout from the
soft-RoCE rig instead of completing the full 160-cycle workload: 4 of the
20 patched runs, and 2 of the 5 unpatched runs that did not oops (the
other 5 unpatched runs time out after the oops). The rig behaves the
same way with and without the patch.
The BUG_ON(!se_tpg) in target_init_cmd() and target_submit_tmr() can be
reached by the same teardown race on fabrics that use those helpers.
iscsit does not - it calls __target_init_cmd() directly and has its own
TMF path - so those paths could not be reproduced or tested here, and
converting a deliberate assertion into graceful failure looked like a
decision for the maintainers rather than something to fold into this fix.
drivers/target/target_core_transport.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
index fad03a15c969..0b292e386691 100644
--- a/drivers/target/target_core_transport.c
+++ b/drivers/target/target_core_transport.c
@@ -904,7 +904,8 @@ static bool target_cmd_interrupted(struct se_cmd *cmd)
static void target_complete(struct se_cmd *cmd, int success)
{
- struct se_wwn *wwn = cmd->se_sess->se_tpg->se_tpg_wwn;
+ struct se_portal_group *se_tpg = READ_ONCE(cmd->se_sess->se_tpg);
+ struct se_wwn *wwn = se_tpg ? se_tpg->se_tpg_wwn : NULL;
struct se_dev_attrib *da;
u8 compl_type;
int cpu;
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] scsi: target: Fix NULL se_tpg dereference in target_complete()
2026-07-25 16:58 [PATCH v2] scsi: target: Fix NULL se_tpg dereference in target_complete() Yehyeong Lee
@ 2026-07-25 20:44 ` Mike Christie
2026-07-26 14:59 ` Yehyeong Lee
0 siblings, 1 reply; 3+ messages in thread
From: Mike Christie @ 2026-07-25 20:44 UTC (permalink / raw)
To: Yehyeong Lee, martin.petersen
Cc: ddiss, linux-scsi, target-devel, linux-kernel, stable
On 7/25/26 11:58 AM, Yehyeong Lee wrote:
> The same statement can fault one level earlier: se_sess->se_tpg itself may
> be NULL. After a session is deregistered, transport_deregister_session()
> clears se_sess->se_tpg, yet the isert receive path can still submit and
> complete a command that references that session, so the backend completion
> runs target_complete() with se_tpg == NULL and dereferences it:
>
> Oops: general protection fault, probably for non-canonical address ...
> KASAN: null-ptr-deref in range [0x0000000000000080-0x0000000000000087]
> Workqueue: ib-comp-wq ib_cq_poll_work
> RIP: 0010:target_complete_cmd_with_sense.part.0+0x17d/0xc90
> Call Trace:
> fd_execute_rw
> __target_execute_cmd
> iscsit_execute_cmd
> iscsit_sequence_cmd
> isert_recv_done
> __ib_process_cq
> ib_cq_poll_work
>
> The exact window in which an isert completion outlives the session
> deregistration has not been pinned down; the guard defends the dereference
> regardless of how the command reaches this point.
>
I think we need to figure out how we got into this situation because we
can't free the session while it's still in use.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] scsi: target: Fix NULL se_tpg dereference in target_complete()
2026-07-25 20:44 ` Mike Christie
@ 2026-07-26 14:59 ` Yehyeong Lee
0 siblings, 0 replies; 3+ messages in thread
From: Yehyeong Lee @ 2026-07-26 14:59 UTC (permalink / raw)
To: michael.christie
Cc: martin.petersen, ddiss, target-devel, linux-scsi, linux-kernel,
stable, yhlee
On 7/26/26 5:44 AM, Mike Christie wrote:
> I think we need to figure out how we got into this situation because we
> can't free the session while it's still in use.
You were right to ask. The session is not being freed - it has not
finished being set up, and this patch is aimed at the wrong place. I am
withdrawing it.
I instrumented transport_deregister_session() and
__transport_register_session() with a silent ring keyed on the
se_session pointer, and printed only from the cold NULL branch. In a
login-churn workload that build recorded nine hits, and every one says
the same thing: the se_session had never passed
transport_deregister_session(); it had a matching
__transport_register_session() record; ktime_get_ns() taken at the read,
before any printk, is earlier than the timestamp taken at the top of
__transport_register_session() in every case; and conn->conn_state was
TARG_CONN_STATE_LOGGED_IN every time.
The window is in login, not teardown. isert_put_login_tx() posts the
full-feature receive buffers and then sends the final Login Response;
iscsi_post_login_handler(), which calls __transport_register_session(),
only runs after that. An initiator that sends a command as soon as it
sees the Login Response gets it received and completed against a session
whose se_tpg is still NULL. The command reaches the backend because
transport_lookup_cmd_lun() does not need se_tpg on the mapped-LUN path -
it uses se_sess->se_node_acl, which iscsit sets much earlier in
iscsi_target_locate_portal().
iscsit's own RX thread is not exposed to this: it waits on
conn->rx_login_comp, which is completed at the end of
iscsi_post_login_handler(), after registration. isert takes its PDUs
from the completion queue instead, and isert_recv_done() has no
connection-state check.
So the commit message on this patch is wrong. It describes a
deregistration window that none of the nine observations involved. I
described a mechanism I had not measured, and I will not do that again.
Guarding target_complete() is also the wrong shape. In the same window
transport_lookup_cmd_lun() dereferences se_sess->se_tpg on the
virtual-LUN-0 fallback, so a command arriving before registration for an
unmapped LUN would fault there instead.
I have posted the isert fix to linux-rdma:
Message-ID: <20260726144213.933544-1-yhlee@isslab.korea.ac.kr>
https://lore.kernel.org/linux-rdma/20260726144213.933544-1-yhlee@isslab.korea.ac.kr/
It moves the isert_post_recvm() call into isert_get_rx_pdu(), which
iscsi_target_rx_thread() invokes after the same rx_login_comp wait, so
the buffers only become available once the session is registered.
Unpatched 9 of 10 runs oops, patched 0 of 10, run alternately in a
single session under KASAN with soft-RoCE.
Please drop this patch.
Best regards,
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-07-26 14:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-07-25 16:58 [PATCH v2] scsi: target: Fix NULL se_tpg dereference in target_complete() Yehyeong Lee
2026-07-25 20:44 ` Mike Christie
2026-07-26 14:59 ` Yehyeong Lee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®