[stgt] segfault when stopping the target

[Tomasz Chmielewski]

This is a tgtadm segfault issue which is reproducible for me:

- configure a target
- connect an initiator
- start such commands (replace with a correct tid, sid, cid):

# tgtadm --op update --mode target --tid=2 -n state -v offline
# tgtadm --op update --mode sys --name State -v offline
# tgtadm --op unbind --mode target --tid 2 -I ALL
# tgtadm --op delete --mode conn --tid 2 --sid 2 --cid 0
Segmentation fault

If a segfault does not happen immediately, start all these commands 
again (or, generally, "tgtadm --op delete --mode conn --tid 2 --sid 1 
--cid 0" is enough).

For me, on x86, segfault happens in 90% of cases. Sometimes, the 
connection is eventually deleted.

# tgtadm --op delete --mode conn --tid 2 --sid 2 --cid 0
Segmentation fault 

# tgtadm --op delete --mode conn --tid 2 --sid 2 --cid 0
Segmentation fault
# tgtadm --op delete --mode conn --tid 2 --sid 2 --cid 0
Segmentation fault
[repeated 11 more times]
# tgtadm --op delete --mode conn --tid 2 --sid 2 --cid 0
#

-- 
Tomasz Chmielewski
http://wpkg.org

--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html