Re: kern/58422: kernel crash when using the iscsi initiator

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR kern/58422; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/58422: kernel crash when using the iscsi initiator
Date: Sat, 13 Jul 2024 07:59:10 -0000 (UTC)

 6bone%6bone.informatik.uni-leipzig.de@localhost writes:
 
 >NetBSD 6bone.informatik.uni-leipzig.de 10.0_STABLE NetBSD 10.0_STABLE (MYCONF10.gdb) #1: Mon Jul  8 15:34:51 CEST 2024  root%6bone.informatik.uni-leipzig.de@localhost:/usr/obj/sys/arch/amd64/compile/MYCONF10.gdb amd64
 
 >[ 85126.220101] cpu2: Begin traceback...
 >[ 85126.220101] vpanic() at netbsd:vpanic+0x183
 >[ 85126.220101] panic() at netbsd:panic+0x3c
 >[ 85126.220101] trap() at netbsd:trap+0xb24
 >[ 85126.220101] --- trap (number 6) ---
 >[ 85126.230191] mutex_enter() at netbsd:mutex_enter+0x3e
 >[ 85126.230191] wake_ccb() at iscsi:wake_ccb+0x8e
 >[ 85126.230191] iscsi_cleanup_thread() at iscsi:iscsi_cleanup_thread+0x351
 >[ 85126.230191] cpu2: End traceback...
 
 
 That's a use-after-free, when a connection is shut down.
 
 The cleanup thread handles timed out CCBs that have already
 been freed with the closing connection.
 
 Can you try to recreate the crash with a DIAGNOSTIC kernel and/or
 set the sysctl hw.iscsi.debug to 9 ?
 
 It might be easier to recreate if you know how the connection
 is shut down. Maybe some reconfig or reboot of the iscsi target
 or some network issue.