[stgt] segfault when stopping the target

[FUJITA Tomonori]

On Tue, 21 Oct 2008 11:41:18 +0200
Tomasz Chmielewski <mangoo at wpkg.org> wrote:

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

Let me make sure I correctly understand the problem you met.

Only tgtadm crashes (tgtd is fine), right?


> - 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 

For example, other commands such as `tgtadm --op show --mode target`
works here, right?


> # 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
--
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