kern/46624: endianess issue in iscsi-target and/or LUN handling bug in iscsi module

[martin%NetBSD.irg@localhost]

>Number:         46624
>Category:       kern
>Synopsis:       endianess issue in iscsi-target and/or LUN handling bug in 
>iscsi module
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 23 11:10:00 +0000 2012
>Originator:     Martin Husemann
>Release:        NetBSD 6.99.7
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD whoever-brings-the-night.aprisoft.de 6.99.7 NetBSD 6.99.7 
(MODULAR) #189: Mon Jun 18 11:01:49 CEST 2012 
martin%emmas.aprisoft.de@localhost:/nelly/usr/src/sys/arch/sparc64/compile/MODULAR
 sparc64
Architecture: sparc64
Machine: sparc64
>Description:
It is very easy to play with iscsi connections on NetBSD (5 or newer). On
one machine, run: "iscsi-target", this will export a single 100MB disk backed
up by storage in /tmp. On the other machine do:

iscsid
iscsictl add_send_target -a (ip-of-target-machine)
iscsictl refresh_targets
iscsictl login -P 2

Now you should get a scsibus and a single sd device attached.

This works with iscsi-target running on i386/amd64 machines. However, if
the target runs on sparc64, you will get sd0, sd1, ... sd15 attached.

This sure looks like a bug in iscsi-target, but testing that target with
Windows shows no duplicated luns - which does not tell much, however.

>How-To-Repeat:
s/a

>Fix:
I'll have a look, but can't right now - filing PR as a reminder.