On Fri, Nov 14, 2014 at 01:46:20PM +0100, Jasper Lievisse Adriaanse wrote:
> Hi,
>
> While playing with iscsid against a Synology NAS I noticed this reproducable
> crash.
> My iscsid.conf:
> --8<--
> target "LUN-1" {
> enabled
> normal
> targetaddr 192.168.178.9
> targetname "iqn.2000-01.com.synology:jabba.Target-1.55f50797a0"
> }
> --8<--
>
> $ sudo iscsid -d -v
> startup
> < now issue iscsictl reload from another terminal, which returns "command
> successful" >
> session_fsm[LUN-1]: INIT ev start timeout 0
> sess_fsm[LUN-1]: INIT ev start
> new connection to 192.168.178.9:3260
> conn_fsm[LUN-1]: FREE ev connect
> conn_fsm[LUN-1]: new state XPT_WAIT
> sess_fsm[LUN-1]: new state FREE
> sess_fsm: done
> conn_fsm[LUN-1]: XPT_WAIT ev connected
> conn_fsm[LUN-1]: new state IN_LOGIN
> bad param TargetPortalGroupTag=0: too small
> SET_NUM: TargetPortalGroupTag = 0
> conn_parse_kvp: errors found
> conn_fail
> conn_fsm[LUN-1]: IN_LOGIN ev fail
> c_do_fail
> session_fsm[LUN-1]: FREE ev connection fail timeout 0
> conn_fsm[LUN-1]: new state FREE
> iscsid(20532) in free(): error: double free 0x14c3e4abe100
> [1] 20532 abort sudo iscsid -d -v
> $
>
> Now I don't even know if my config is correct, but this double free doesn't
> look quite correct either:
Note the double free was from running with MALLOC_OPTIONS=j, whereas the trace
below was obtained with it set to S.
--
jasper
