[PATCH] initd.redhat: Add iSER to initd.redhat
Erez Zilber
The patch was made over r716.
--
____________________________________________________________
Erez Zilber | 972-9-971-7689
Software Engineer, Storage Team
Voltaire – _The Grid Backbone_
__
www.voltaire.com <http://www.voltaire.com/>
Albert Pauw
ib_iser module
(from dmesg):
Loading iSCSI transport class v2.0-711.
iscsi: registered transport (tcp)
ib_iser: disagrees about version of symbol iscsi_conn_setup
ib_iser: Unknown symbol iscsi_conn_setup
ib_iser: disagrees about version of symbol iscsi_verify_itt
ib_iser: Unknown symbol iscsi_verify_itt
ib_iser: disagrees about version of symbol
iscsi_session_recovery_timedout
ib_iser: Unknown symbol iscsi_session_recovery_timedout
ib_iser: disagrees about version of symbol iscsi_conn_bind
ib_iser: Unknown symbol iscsi_conn_bind
ib_iser: disagrees about version of symbol iscsi_session_setup
ib_iser: Unknown symbol iscsi_session_setup
ib_iser: disagrees about version of symbol class_to_transport_session
ib_iser: Unknown symbol class_to_transport_session
ib_iser: disagrees about version of symbol iscsi_conn_failure
ib_iser: Unknown symbol iscsi_conn_failure
ib_iser: disagrees about version of symbol iscsi_complete_pdu
ib_iser: Unknown symbol iscsi_complete_pdu
ib_iser: disagrees about version of symbol iscsi_register_transport
ib_iser: Unknown symbol iscsi_register_transport
ib_iser: disagrees about version of symbol iscsi_set_param
ib_iser: Unknown symbol iscsi_set_param
ib_iser: disagrees about version of symbol iscsi_conn_get_param
ib_iser: Unknown symbol iscsi_conn_get_param
ib_iser: disagrees about version of symbol iscsi_conn_teardown
ib_iser: Unknown symbol iscsi_conn_teardown
ib_iser: disagrees about version of symbol iscsi_session_get_param
ib_iser: Unknown symbol iscsi_session_get_param
ib_iser: disagrees about version of symbol iscsi_conn_send_pdu
ib_iser: Unknown symbol iscsi_conn_send_pdu
ib_iser: disagrees about version of symbol iscsi_conn_start
ib_iser: Unknown symbol iscsi_conn_start
ib_iser: disagrees about version of symbol
iscsi_prep_unsolicit_data_pdu
ib_iser: Unknown symbol iscsi_prep_unsolicit_data_pdu
ib_iser: disagrees about version of symbol iscsi_session_teardown
ib_iser: Unknown symbol iscsi_session_teardown
ib_iser: disagrees about version of symbol iscsi_unregister_transport
ib_iser: Unknown symbol iscsi_unregister_transport
ib_iser: disagrees about version of symbol iscsi_conn_stop
ib_iser: Unknown symbol iscsi_conn_stop
Erez Zilber
> Using FC5 kernel 2.6.18-1 (latest release) I have problems loading the
> ib_iser module
> (from dmesg):
>
> Loading iSCSI transport class v2.0-711.
> iscsi: registered transport (tcp)
> ib_iser: disagrees about version of symbol iscsi_conn_setup
> ib_iser: Unknown symbol iscsi_conn_setup
>
kernel tree? This may explain this behavior.
I have a beta version of RHEL5 (BTW - how can I know which beta version
do I have?) and I replaced the kernel to 2.6.18-1.2798.fc6 and I'm using
iscsi-initiator-utils-6.2.0.695-0.8.el5.src.rpm for the userspace part.
I applied the patch that I've just sent and was able to start open-iscsi
over iSER.
Erez
Albert Pauw
Then installed open-iscsi svn 716, compiled, installed.
Here is the info of the iser module which came with this kernel:
[root@orange iser]# modinfo ib_iser.ko
filename: ib_iser.ko
description: iSER (iSCSI Extensions for RDMA) Datamover v0.1 (May
7th, 2006)
license: Dual BSD/GPL
author: Alex Nezhinsky, Dan Bar Dov, Or Gerlitz
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: ib_core,libiscsi,scsi_transport_iscsi,rdma_cm,scsi_mod
srcversion: 3D0397455EE189336A60922
parm: debug_level:Enable debug tracing if > 0
(default:disabled) (int)parm: max_lun:uint
Erez Zilber
> Used the standard one, latest version (2.6.18-1.2200.fc5).
> Then installed open-iscsi svn 716, compiled, installed.
>
Erez
Mike Christie
> Albert Pauw wrote:
>> Using FC5 kernel 2.6.18-1 (latest release) I have problems loading the
>> ib_iser module
>> (from dmesg):
>>
>> Loading iSCSI transport class v2.0-711.
>> iscsi: registered transport (tcp)
>> ib_iser: disagrees about version of symbol iscsi_conn_setup
>> ib_iser: Unknown symbol iscsi_conn_setup
>>
> This looks very strange. Did you build open-iscsi modules out of the
> kernel tree? This may explain this behavior.
>
> I have a beta version of RHEL5 (BTW - how can I know which beta version
cat /etc/redhat-release
may have the info. It is probably not as finely grained as what beta
snapshot - maybe just the major snapshot version.
Albert Pauw
Fedora Core release 5 (Bordeaux)
Erez Zilber
[root@rosemary ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 4.91 (Tikanga)
Albert - did you try running the original open-iscsi code (the one that
comes with the original kernel)? Do you still see that error when
loading ib_iser?
Albert Pauw
> comes with the original kernel)? Do you still see that error when
> loading ib_iser?
what's a quick way to get it again?
Erez Zilber
from the rpm and put them in /lib/modules/`uname -r` instead of your
modules.
Erez
Albert Pauw
with the original one coming with the kernel itself. That's all I
changed (iscsiadm, scripts, etc all from svn 716) and it now loads the
isermodule fine, from dmesg:
Loading iSCSI transport class v1.1-646.<5>iscsi: registered transport
(tcp)
iscsi: registered transport (iser)
I tried login into a target, run an hdparm -t on it. Works fine.
[root@orange apauw]# lsmod | grep iser
ib_iser 33965 0
rdma_cm 21957 1 ib_iser
ib_core 49985 5 ib_iser,rdma_cm,ib_cm,ib_sa,ib_mad
libiscsi 24385 2 ib_iser,iscsi_tcp
scsi_transport_iscsi 29901 4 ib_iser,iscsi_tcp,libiscsi
scsi_mod 134121 8
ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,sg,ahci,libata,sd_mod
But installing the latest kernel modules (svn r716) is a no go with the
ib_iser module, as shown above.
Erez Zilber
scsi_transport_iscsi" on the original and new modules. I think that the
problem is not with iSER - it is with your new open-iscsi modules. They
don't match with the kernel version. Run also "modinfo ib_iser" and
you'll see that its version matches with the original open-iscsi modules.
Albert Pauw
[root@orange ~]# modinfo libiscsi
filename:
/lib/modules/2.6.18-1.2200.fc5/kernel/drivers/scsi/libiscsi.ko
author: Mike Christie
description: iSCSI library functions
license: GPL
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: scsi_mod,scsi_transport_iscsi
srcversion: BC67A0B215C61D8AF5F3DB7
[root@orange ~]# modinfo scsi_transport_iscsi
filename:
/lib/modules/2.6.18-1.2200.fc5/kernel/drivers/scsi/scsi_transport_iscsi.ko
author: Mike Christie <mich...@cs.wisc.edu>, Dmitry Yusupov
<dmitr...@yahoo.com>, Alex Aizman <itn...@yahoo.com>
description: iSCSI Transport Interface
license: GPL
version: 1.1-646
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: scsi_mod
srcversion: F81B98425B194A808D84DBE
[root@orange ~]# modinfo iscsi_tcp
filename:
/lib/modules/2.6.18-1.2200.fc5/kernel/drivers/scsi/iscsi_tcp.ko
author: Dmitry Yusupov <dmitr...@yahoo.com>, Alex Aizman
<itn...@yahoo.com>
description: iSCSI/TCP data-path
license: GPL
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: libiscsi,scsi_transport_iscsi,scsi_mod
srcversion: A29791BA778DE12D0856A0A
parm: max_lun:uint
[root@orange ~]# modinfo ib_iser
filename:
/lib/modules/2.6.18-1.2200.fc5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko
description: iSER (iSCSI Extensions for RDMA) Datamover v0.1 (May
7th, 2006)
license: Dual BSD/GPL
author: Alex Nezhinsky, Dan Bar Dov, Or Gerlitz
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: ib_core,libiscsi,scsi_transport_iscsi,rdma_cm,scsi_mod
srcversion: 3D0397455EE189336A60922
parm: debug_level:Enable debug tracing if > 0
(default:disabled) (int)parm: max_lun:uint
Now the svn r716 ones:
[root@orange kernel]# modinfo ./libiscsi.ko
filename: ./libiscsi.ko
author: Mike Christie
description: iSCSI library functions
license: GPL
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: scsi_mod,scsi_transport_iscsi
srcversion: 1A08E45AFE6EB58CD126C8F
[root@orange kernel]# modinfo ./scsi_transport_iscsi.ko
filename: ./scsi_transport_iscsi.ko
author: Mike Christie <mich...@cs.wisc.edu>, Dmitry Yusupov
<dmitr...@yahoo.com>, Alex Aizman <itn...@yahoo.com>
description: iSCSI Transport Interface
license: GPL
version: 2.0-711
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: scsi_mod
srcversion: 31C6F675F58E1B73AB7C92B
[root@orange kernel]# modinfo ./iscsi_tcp.ko
filename: ./iscsi_tcp.ko
author: Dmitry Yusupov <dmitr...@yahoo.com>, Alex Aizman
<itn...@yahoo.com>
description: iSCSI/TCP data-path
license: GPL
vermagic: 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
depends: libiscsi,scsi_transport_iscsi,scsi_mod
srcversion: DE4E2F0B431405516D49771
parm: max_lun:uint
Erez Zilber
The problem is that you build open-iscsi out of tree. Because of that,
/lib/modules/`uname -r`/build/Module.symvers is not updated with the new
symbols. Try to run the following commands:
nm /lib/modules/`uname -r`/kernel/drivers/scsi/libiscsi.ko | grep
iscsi_conn_setup
nm <r716>/open-iscsi/kernel/libiscsi.ko | grep iscsi_conn_setup
cat /lib/modules/`uname -r`/build/Module.symvers |grep iscsi_conn_setup
You'll see that the versions don't match.
I tried the same thing on my RHEL 5 machine. I was lucky because the
version of open-iscsi in the kernel & r716 are identical. You run a
different kernel and this is why you fail. Here are my results:
[root@rosemary linux-2.6.18.x86_64]# nm
/lib/modules/2.6.18-prep/kernel/drivers/scsi/libiscsi.ko |grep
iscsi_conn_setup
000000008d9291fa A __crc_iscsi_conn_setup < -- This one is interesting
(you'll probably see a different number here)
0000000000000038 r __kcrctab_iscsi_conn_setup
00000000000000b0 r __kstrtab_iscsi_conn_setup
0000000000000070 r __ksymtab_iscsi_conn_setup
0000000000001eab T iscsi_conn_setup
[root@rosemary linux-2.6.18.x86_64]# nm
/home/erezz/work/open-iscsi/tmp/r716/open-iscsi/kernel/libiscsi.ko |grep
iscsi_conn_setup
000000008d9291fa A __crc_iscsi_conn_setup < -- This one is interesting
0000000000000038 r __kcrctab_iscsi_conn_setup
00000000000000b0 r __kstrtab_iscsi_conn_setup
0000000000000070 r __ksymtab_iscsi_conn_setup
0000000000001eab T iscsi_conn_setup
[root@rosemary linux-2.6.18.x86_64]# cat
/lib/modules/2.6.18-prep/build/Module.symvers |grep iscsi_conn_setup
0x8d9291fa iscsi_conn_setup drivers/scsi/libiscsi EXPORT_SYMBOL_GPL
If this is the problem, I can give you several solutions.
Albert Pauw
you where absolutely right:
[root@orange ~]# nm /lib/modules/`uname
-r`/kernel/drivers/scsi/libiscsi.ko | grep iscsi_conn_setup
2f1913dc A __crc_iscsi_conn_setup
00001ba4 T iscsi_conn_setup
00000048 r __kcrctab_iscsi_conn_setup
0000018e r __kstrtab_iscsi_conn_setup
00000090 r __ksymtab_iscsi_conn_setup
[root@orange ~]# nm /usr/src/redhat/BUILD/open-iscsi/kernel/libiscsi.ko
| grep iscsi_conn_setup
461cb302 A __crc_iscsi_conn_setup
00001c72 T iscsi_conn_setup
00000048 r __kcrctab_iscsi_conn_setup
0000018e r __kstrtab_iscsi_conn_setup
00000090 r __ksymtab_iscsi_conn_setup
[root@orange ~]# cat
/lib/modules/2.6.18-1.2200.fc5/build/Module.symvers | grep
iscsi_conn_setup
0x2f1913dc iscsi_conn_setup drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
Would it be possible to stick the different version number in
Module.symvers, in my case
461cb302?
If so, would it be an idea to have the Makefile make this modification
when it installs the modules?
Erez Zilber
I've attached a script that we use to do that. You may need to make very
small fixes in order to make it work. It creates a patch and applies it
on Module.symvers. Let me know if you managed to use it. Adding it to
the kernel Makefile is a good idea.
Albert Pauw
source, otherwise it wouldn't find the .ko modules.
Here's wat the output is:
[root@orange kernel]# ../fix_symvers.bash
mod = iscsi_tcp.ko
/tmp/syms
mod = libiscsi.ko
/tmp/syms
mod = scsi_transport_iscsi.ko
/tmp/syms
found 42 open-iscsi symbols in 3 open-iscsi modules
[root@orange kernel]# depmod -aq
[root@orange kernel]# service open-iscsi stop
Stopping iSCSI initiator service: [ OK ]
[root@orange kernel]# service open-iscsi start
Starting iSCSI initiator service: FATAL: Error inserting ib_iser
(/lib/modules/2.6.18-1.2200.fc5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
[ OK ]
Setting up iSCSI targets: iscsiadm: initiator reported error (4 -
encountered connection failure)
[ OK ]
Erez Zilber
Albert Pauw
iscsi: registered transport (tcp)
ib_iser: disagrees about version of symbol iscsi_conn_setup
ib_iser: Unknown symbol iscsi_conn_setup
Erez Zilber
with the version. Can you send again the output of:
nm /lib/modules/`uname -r`/kernel/drivers/scsi/libiscsi.ko | grep iscsi_conn_setup
nm /usr/src/redhat/BUILD/open-iscsi/kernel/libiscsi.ko
cat /lib/modules/2.6.18-1.2200.fc5/build/Module.symvers | grep iscsi_conn_setup
Albert Pauw
-r`/kernel/drivers/scsi/libiscsi.ko | grep iscsi_conn_setup
461cb302 A __crc_iscsi_conn_setup
00001c72 T iscsi_conn_setup
00000048 r __kcrctab_iscsi_conn_setup
0000018e r __kstrtab_iscsi_conn_setup
00000090 r __ksymtab_iscsi_conn_setup
U autoremove_wake_function
000002cc T class_to_transport_session
8829b2c3 A __crc_class_to_transport_session
7452449d A __crc_iscsi_change_queue_depth
5252c534 A __crc_iscsi_check_assign_cmdsn
c7d65656 A __crc___iscsi_complete_pdu
9efdf951 A __crc_iscsi_complete_pdu
b8528221 A __crc_iscsi_conn_bind
a1a1abcb A __crc_iscsi_conn_failure
47580196 A __crc_iscsi_conn_get_param
047f7b4a A __crc_iscsi_conn_send_pdu
461cb302 A __crc_iscsi_conn_setup
d6316a68 A __crc_iscsi_conn_start
57171366 A __crc_iscsi_conn_stop
fbe923d2 A __crc_iscsi_conn_teardown
bc11bbc3 A __crc_iscsi_eh_abort
f89a0abd A __crc_iscsi_eh_host_reset
5df3cb80 A __crc_iscsi_pool_free
e71028ea A __crc_iscsi_pool_init
60b5118e A __crc_iscsi_prep_scsi_cmd_pdu
0db777cf A __crc_iscsi_prep_unsolicit_data_pdu
b98bbbfb A __crc_iscsi_queuecommand
ca5a2f62 A __crc_iscsi_session_get_param
5a12ad76 A __crc_iscsi_session_recovery_timedout
112ec66a A __crc_iscsi_session_setup
2e9ccb24 A __crc_iscsi_session_teardown
18532f2d A __crc_iscsi_set_param
760e7906 A __crc_iscsi_verify_itt
U del_timer
000006e2 t fail_command
U finish_wait
U flush_signals
U init_timer
U init_waitqueue_head
U int_to_scsilun
U iscsi_block_session
00001142 T iscsi_change_queue_depth
000001ed T iscsi_check_assign_cmdsn
0000158b T __iscsi_complete_pdu
000019af T iscsi_complete_pdu
000019ec T iscsi_conn_bind
U iscsi_conn_error
0000117f T iscsi_conn_failure
00000240 T iscsi_conn_get_param
00000f66 t iscsi_conn_send_generic
00001104 T iscsi_conn_send_pdu
00001c72 T iscsi_conn_setup
0000090b T iscsi_conn_start
00000721 T iscsi_conn_stop
00000a60 T iscsi_conn_teardown
U iscsi_create_conn
U iscsi_create_session
00000644 t iscsi_ctask_mtask_cleanup
U iscsi_destroy_conn
U iscsi_destroy_session
000011d8 T iscsi_eh_abort
00001e8a T iscsi_eh_host_reset
00000a35 T iscsi_pool_free
00000de5 T iscsi_pool_init
00000000 t iscsi_prep_scsi_cmd_pdu
00001a2d T iscsi_prep_unsolicit_data_pdu
000005db t __iscsi_put_ctask
00001ade T iscsi_queuecommand
U iscsi_recv_pdu
000002fb T iscsi_session_get_param
000009e3 T iscsi_session_recovery_timedout
00001fd9 T iscsi_session_setup
00001df4 T iscsi_session_teardown
000003b6 T iscsi_set_param
00000f18 t iscsi_tmabort_timedout
U iscsi_unblock_session
000004fa T iscsi_verify_itt
00000bb6 t iscsi_xmitworker
U jiffies
00000000 r __kcrctab_class_to_transport_session
00000024 r __kcrctab_iscsi_change_queue_depth
00000004 r __kcrctab_iscsi_check_assign_cmdsn
00000010 r __kcrctab___iscsi_complete_pdu
00000014 r __kcrctab_iscsi_complete_pdu
00000058 r __kcrctab_iscsi_conn_bind
0000001c r __kcrctab_iscsi_conn_failure
00000064 r __kcrctab_iscsi_conn_get_param
00000028 r __kcrctab_iscsi_conn_send_pdu
00000048 r __kcrctab_iscsi_conn_setup
00000050 r __kcrctab_iscsi_conn_start
00000054 r __kcrctab_iscsi_conn_stop
0000004c r __kcrctab_iscsi_conn_teardown
00000034 r __kcrctab_iscsi_eh_abort
00000030 r __kcrctab_iscsi_eh_host_reset
0000003c r __kcrctab_iscsi_pool_free
00000038 r __kcrctab_iscsi_pool_init
0000000c r __kcrctab_iscsi_prep_scsi_cmd_pdu
00000008 r __kcrctab_iscsi_prep_unsolicit_data_pdu
00000020 r __kcrctab_iscsi_queuecommand
00000060 r __kcrctab_iscsi_session_get_param
0000002c r __kcrctab_iscsi_session_recovery_timedout
00000040 r __kcrctab_iscsi_session_setup
00000044 r __kcrctab_iscsi_session_teardown
0000005c r __kcrctab_iscsi_set_param
00000018 r __kcrctab_iscsi_verify_itt
00000000 b __key.31685
00000000 b __key.31786
U kfifo_alloc
U kfifo_free
U __kfifo_get
U kfifo_init
U __kfifo_put
U kfree
U __kmalloc
U kmem_cache_alloc
U kstrdup
00000000 r __kstrtab_class_to_transport_session
000000c9 r __kstrtab_iscsi_change_queue_depth
0000001b r __kstrtab_iscsi_check_assign_cmdsn
0000006a r __kstrtab___iscsi_complete_pdu
0000007f r __kstrtab_iscsi_complete_pdu
000001d4 r __kstrtab_iscsi_conn_bind
000000a3 r __kstrtab_iscsi_conn_failure
0000020c r __kstrtab_iscsi_conn_get_param
000000e2 r __kstrtab_iscsi_conn_send_pdu
0000018e r __kstrtab_iscsi_conn_setup
000001b3 r __kstrtab_iscsi_conn_start
000001c4 r __kstrtab_iscsi_conn_stop
0000019f r __kstrtab_iscsi_conn_teardown
00000134 r __kstrtab_iscsi_eh_abort
00000120 r __kstrtab_iscsi_eh_host_reset
00000153 r __kstrtab_iscsi_pool_free
00000143 r __kstrtab_iscsi_pool_init
00000052 r __kstrtab_iscsi_prep_scsi_cmd_pdu
00000034 r __kstrtab_iscsi_prep_unsolicit_data_pdu
000000b6 r __kstrtab_iscsi_queuecommand
000001f4 r __kstrtab_iscsi_session_get_param
00000100 r __kstrtab_iscsi_session_recovery_timedout
00000163 r __kstrtab_iscsi_session_setup
00000177 r __kstrtab_iscsi_session_teardown
000001e4 r __kstrtab_iscsi_set_param
00000092 r __kstrtab_iscsi_verify_itt
00000000 r __ksymtab_class_to_transport_session
00000048 r __ksymtab_iscsi_change_queue_depth
00000008 r __ksymtab_iscsi_check_assign_cmdsn
00000020 r __ksymtab___iscsi_complete_pdu
00000028 r __ksymtab_iscsi_complete_pdu
000000b0 r __ksymtab_iscsi_conn_bind
00000038 r __ksymtab_iscsi_conn_failure
000000c8 r __ksymtab_iscsi_conn_get_param
00000050 r __ksymtab_iscsi_conn_send_pdu
00000090 r __ksymtab_iscsi_conn_setup
000000a0 r __ksymtab_iscsi_conn_start
000000a8 r __ksymtab_iscsi_conn_stop
00000098 r __ksymtab_iscsi_conn_teardown
00000068 r __ksymtab_iscsi_eh_abort
00000060 r __ksymtab_iscsi_eh_host_reset
00000078 r __ksymtab_iscsi_pool_free
00000070 r __ksymtab_iscsi_pool_init
00000018 r __ksymtab_iscsi_prep_scsi_cmd_pdu
00000010 r __ksymtab_iscsi_prep_unsolicit_data_pdu
00000040 r __ksymtab_iscsi_queuecommand
000000c0 r __ksymtab_iscsi_session_get_param
00000058 r __ksymtab_iscsi_session_recovery_timedout
00000080 r __ksymtab_iscsi_session_setup
00000088 r __ksymtab_iscsi_session_teardown
000000b8 r __ksymtab_iscsi_set_param
00000030 r __ksymtab_iscsi_verify_itt
U __list_add
U list_del
U malloc_sizes
00000000 r __mod_author1971
00000020 r __mod_description1972
00000044 r __mod_license1973
000000c0 r __mod_srcversion31
U __mod_timer
000000a3 r __module_depends
00000060 r __mod_vermagic5
U msleep_interruptible
U __mutex_init
U mutex_lock
U mutex_unlock
U prepare_to_wait
U printk
U schedule
U scsi_add_host
U scsi_adjust_queue_depth
U scsi_host_alloc
U scsi_host_put
U scsi_is_host_device
U scsi_queue_work
U scsi_remove_host
U _spin_lock
U _spin_lock_bh
U __spin_lock_init
U _spin_lock_irqsave
U _spin_unlock
U _spin_unlock_bh
U _spin_unlock_irqrestore
U sprintf
U sscanf
00000000 D __this_module
00000000 r ____versions
U __wake_up
U wake_up_process
U _write_lock_bh
U _write_unlock_bh
[root@orange ~]# cat
/lib/modules/2.6.18-1.2200.fc5/build/Module.symvers | grep
iscsi_conn_setup
Erez Zilber
> [root@orange ~]# nm /lib/modules/`uname
> -r`/kernel/drivers/scsi/libiscsi.ko | grep iscsi_conn_setup
> 461cb302 A __crc_iscsi_conn_setup
>
did it change? Did you replace the module?
> 00001c72 T iscsi_conn_setup
> 00000048 r __kcrctab_iscsi_conn_setup
> 0000018e r __kstrtab_iscsi_conn_setup
> 00000090 r __ksymtab_iscsi_conn_setup
> [root@orange ~]# nm /usr/src/redhat/BUILD/open-iscsi/kernel/libiscsi.ko
> U autoremove_wake_function
> 000002cc T class_to_transport_session
> 8829b2c3 A __crc_class_to_transport_session
> 7452449d A __crc_iscsi_change_queue_depth
> 5252c534 A __crc_iscsi_check_assign_cmdsn
> c7d65656 A __crc___iscsi_complete_pdu
> 9efdf951 A __crc_iscsi_complete_pdu
> b8528221 A __crc_iscsi_conn_bind
> a1a1abcb A __crc_iscsi_conn_failure
> 47580196 A __crc_iscsi_conn_get_param
> 047f7b4a A __crc_iscsi_conn_send_pdu
> 461cb302 A __crc_iscsi_conn_setup
>
0x461cb302 iscsi_conn_setup drivers/scsi/libiscsi
You can return to the initial state by applying the patch
(/tmp/Module.symvers.patch) in reverse mode. Then you can check what
went wrong.
Albert Pauw
> You can return to the initial state by applying the patch
> (/tmp/Module.symvers.patch) in reverse mode. Then you can check what
> went wrong.
There's nu such thing in my /tmp directory, so I can't check that.
I tried removing the kernel-devel package and reinstall again. Don't
know if I would get the original Module.symvers back.
Anyway, I just used the Makefile in the open-iscsi source to install.
This should have replaced the modules properly by the new ones.
Albert Pauw
Anyway removing and re-installing kernel-devel gives me back the
original Modules.symvers.
I reinstalled again open-iscsi, did a depmod -aq, run your script and
made a diff between the original Modules.symvers and the newly
generated one. Here's the diff (-ruN format):
--- Module.symvers 2006-10-29 17:58:46.000000000 +0100
+++ Module.symvers.org 2006-10-29 17:53:15.000000000 +0100
@@ -1,45 +1,3 @@
-0x class_to_transport_session libiscsi
-0x iscsi_change_queue_depth libiscsi
-0x iscsi_check_assign_cmdsn libiscsi
-0x __iscsi_complete_pdu libiscsi
-0x iscsi_complete_pdu libiscsi
-0x iscsi_conn_bind libiscsi
-0x iscsi_conn_failure libiscsi
-0x iscsi_conn_get_param libiscsi
-0x iscsi_conn_send_pdu libiscsi
-0x iscsi_conn_setup libiscsi
-0x iscsi_conn_start libiscsi
-0x iscsi_conn_stop libiscsi
-0x iscsi_conn_teardown libiscsi
-0x iscsi_eh_abort libiscsi
-0x iscsi_eh_host_reset libiscsi
-0x iscsi_pool_free libiscsi
-0x iscsi_pool_init libiscsi
-0x iscsi_prep_scsi_cmd_pdu libiscsi
-0x iscsi_prep_unsolicit_data_pdu libiscsi
-0x iscsi_queuecommand libiscsi
-0x iscsi_session_get_param libiscsi
-0x iscsi_session_recovery_timedout libiscsi
-0x iscsi_session_setup libiscsi
-0x iscsi_session_teardown libiscsi
-0x iscsi_set_param libiscsi
-0x iscsi_verify_itt libiscsi
-0x iscsi_add_session scsi_transport_iscsi
-0x iscsi_alloc_session scsi_transport_iscsi
-0x iscsi_block_session scsi_transport_iscsi
-0x iscsi_conn_error scsi_transport_iscsi
-0x iscsi_create_conn scsi_transport_iscsi
-0x iscsi_create_session scsi_transport_iscsi
-0x iscsi_destroy_conn scsi_transport_iscsi
-0x iscsi_destroy_session scsi_transport_iscsi
-0x iscsi_free_session scsi_transport_iscsi
-0x iscsi_if_create_session_done scsi_transport_iscsi
-0x iscsi_if_destroy_session_done scsi_transport_iscsi
-0x iscsi_recv_pdu scsi_transport_iscsi
-0x iscsi_register_transport scsi_transport_iscsi
-0x iscsi_remove_session scsi_transport_iscsi
-0x iscsi_unblock_session scsi_transport_iscsi
-0x iscsi_unregister_transport scsi_transport_iscsi
0x88b73627 tipc_get_addr net/tipc/tipc EXPORT_SYMBOL
0x6fb5ab71 mpt_deregister drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x4266f38c firmware_unregister vmlinux EXPORT_SYMBOL_GPL
@@ -108,6 +66,7 @@
0x347a20b7 dvb_pll_philips_sd1878_tda8261
drivers/media/dvb/frontends/dvb-pll EXPORT_SYMBOL
0xf6e19955 transport_class_register vmlinux
EXPORT_SYMBOL_GPL
0x2f85bbbe snd_emux_terminate_all sound/synth/emux/snd-emux-synth
EXPORT_SYMBOL
+0x2f1913dc iscsi_conn_setup drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x4459fd47 mpt_free_fw_memory drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x53928019 dm_put_device drivers/md/dm-mod EXPORT_SYMBOL
0xee1b7bd4 dm_get_device drivers/md/dm-mod EXPORT_SYMBOL
@@ -947,6 +906,7 @@
0x5b49d5ce nobh_commit_write vmlinux EXPORT_SYMBOL
0x3ed5142b ip_ct_iterate_cleanup net/ipv4/netfilter/ip_conntrack
EXPORT_SYMBOL
0x2be5133a scsi_is_sdev_device drivers/scsi/scsi_mod
EXPORT_SYMBOL
+0x77cfc2dd class_to_transport_session drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd15db3dd sk_free vmlinux EXPORT_SYMBOL
0x02cd3086 __down_failed_trylock vmlinux EXPORT_SYMBOL
0x28c68196 ieee80211softmac_notify_gfp
net/ieee80211/softmac/ieee80211softmac EXPORT_SYMBOL_GPL
@@ -1079,6 +1039,7 @@
0x84e531af iput vmlinux EXPORT_SYMBOL
0xd072a79c sleep_on_timeout vmlinux EXPORT_SYMBOL
0x5a157ae4 nfs4_acl_get_whotype fs/nfsd/nfsd EXPORT_SYMBOL
+0xbd95d973 iscsi_alloc_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x8f18b846 cx88_shutdown drivers/media/video/cx88/cx88xx
EXPORT_SYMBOL
0xd96bca50 hpsb_packet_sent drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xebf91792 create_proc_entry vmlinux EXPORT_SYMBOL
@@ -1092,6 +1053,7 @@
0x7aa4ff90 neigh_event_ns vmlinux EXPORT_SYMBOL
0xd5e1f1a4 fb_firmware_edid vmlinux EXPORT_SYMBOL
0x01ac0524 key_negate_and_link vmlinux EXPORT_SYMBOL
+0xb98bbbfb iscsi_queuecommand drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x85839d63 hpsb_unregister_highlevel
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x88ee4764 request_firmware_nowait vmlinux EXPORT_SYMBOL
0xd08197fa acpi_load_tables vmlinux EXPORT_SYMBOL
@@ -1238,6 +1200,7 @@
0xe8cb825f complete vmlinux EXPORT_SYMBOL
0xb703874c snd_hda_bus_new sound/pci/hda/snd-hda-codec
EXPORT_SYMBOL
0xf81a8679 config_item_init_type_name fs/configfs/configfs
EXPORT_SYMBOL
+0xe314f4f9 iscsi_block_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x02ba2212 ata_port_freeze drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x5b9da9ae ata_bmdma_start drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x6ade8b24 __gameport_register_driver
drivers/input/gameport/gameport EXPORT_SYMBOL
@@ -1294,6 +1257,7 @@
0xaaa1d535 inet_dgram_connect vmlinux EXPORT_SYMBOL
0xff56c944 driver_unregister vmlinux EXPORT_SYMBOL_GPL
0x2b5311e6 end_that_request_first vmlinux EXPORT_SYMBOL
+0x78ff005a iscsi_unblock_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x5ebefe4b v4l_printk_ioctl drivers/media/video/v4l2-common
EXPORT_SYMBOL
0xe3cd9b5c saa7146_debug drivers/media/common/saa7146
EXPORT_SYMBOL_GPL
0xac6acb48 kobject_put vmlinux EXPORT_SYMBOL
@@ -1417,6 +1381,7 @@
0x87754115 raw_notifier_chain_register vmlinux
EXPORT_SYMBOL_GPL
0x6b5e3f2c snd_midi_event_decode
sound/core/seq/snd-seq-midi-event EXPORT_SYMBOL
0x2ae981ab scsi_host_alloc drivers/scsi/scsi_mod EXPORT_SYMBOL
+0xf89a0abd iscsi_eh_host_reset drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf7c5f008 cdrom_get_media_event drivers/cdrom/cdrom
EXPORT_SYMBOL
0xcffb4fb8 pcmcia_get_configuration_info vmlinux EXPORT_SYMBOL
0x79e4fd48 sysfs_remove_file vmlinux EXPORT_SYMBOL_GPL
@@ -1588,6 +1553,7 @@
0x7372acdc cpufreq_cpu_get vmlinux EXPORT_SYMBOL_GPL
0xba8d1777 free_buffer_head vmlinux EXPORT_SYMBOL
0x9e4a7595 fget vmlinux EXPORT_SYMBOL
+0x398d20f8 iscsi_complete_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf71f5871 phy_sanitize_settings drivers/net/phy/libphy
EXPORT_SYMBOL
0x62c4760f ide_config_drive_speed vmlinux EXPORT_SYMBOL
0x2dd1d503 rdc_8820_reset drivers/media/dvb/bt8xx/dst
EXPORT_SYMBOL
@@ -1667,6 +1633,7 @@
0xa5c79544 switch_APIC_timer_to_ipi vmlinux EXPORT_SYMBOL
0x5426a49a snd_cs4231_mce_down sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0xfdc1b546 cache_check net/sunrpc/sunrpc EXPORT_SYMBOL
+0x28eedccb iscsi_destroy_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd32b89e3 video_usercopy drivers/media/video/videodev
EXPORT_SYMBOL
0x5dbaffb1 usb_check_bandwidth vmlinux EXPORT_SYMBOL
0x01438985 acpi_fadt_is_v1 vmlinux EXPORT_SYMBOL
@@ -1891,6 +1858,7 @@
0x0a7a2ab5 snd_card_file_remove sound/core/snd EXPORT_SYMBOL
0x3b91f3af snd_free_pages sound/core/snd-page-alloc
EXPORT_SYMBOL
0x1432a31b o2nm_get_node_by_num
fs/ocfs2/cluster/ocfs2_nodemanager EXPORT_SYMBOL_GPL
+0x1aac80db __iscsi_complete_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x858136e4 usb_init_urb vmlinux EXPORT_SYMBOL
0x85e5a3db ktime_get_ts vmlinux EXPORT_SYMBOL_GPL
0x5a4896a8 __put_user_2 vmlinux EXPORT_SYMBOL
@@ -2044,6 +2012,7 @@
0x7ddcee1c inet_dccp_listen net/dccp/dccp
EXPORT_SYMBOL_GPL
0x688c7ce0 irda_register_dongle drivers/net/irda/sir-dev
EXPORT_SYMBOL
0x263b54cc acpi_resource_to_address64 vmlinux EXPORT_SYMBOL
+0xdb016841 iscsi_conn_stop drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x25a7ebdf proc_dointvec_minmax vmlinux EXPORT_SYMBOL
0x3c9435bf atm_charge net/atm/atm EXPORT_SYMBOL
0x3811daea ir_codes_manli drivers/media/common/ir-common
EXPORT_SYMBOL_GPL
@@ -2076,6 +2045,7 @@
0x76670e30 snd_vx_check_reg_bit sound/drivers/vx/snd-vx-lib
EXPORT_SYMBOL
0xd93f48d8 snd_seq_instr_free_use sound/core/seq/snd-seq-instr
EXPORT_SYMBOL
0xbaeb4700 o2hb_check_node_heartbeating_from_callback
fs/ocfs2/cluster/ocfs2_nodemanager EXPORT_SYMBOL_GPL
+0x311e4995 iscsi_conn_start drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd8b1bf0c ethtool_op_set_tx_hw_csum vmlinux EXPORT_SYMBOL
0x2ea16d99 end_that_request_chunk vmlinux EXPORT_SYMBOL
0x6ba6444c dvb_ringbuffer_pkt_write
drivers/media/dvb/dvb-core/dvb-core EXPORT_SYMBOL
@@ -2353,6 +2323,7 @@
0x7f0d89cc gigaset_freedriver drivers/isdn/gigaset/gigaset
EXPORT_SYMBOL_GPL
0x23679939 __iowrite32_copy vmlinux EXPORT_SYMBOL_GPL
0x7149979e xdr_enter_page net/sunrpc/sunrpc EXPORT_SYMBOL
+0xadd2f52f iscsi_create_conn
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x647b4230 ata_do_eh drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x612390ad netpoll_set_trap vmlinux EXPORT_SYMBOL
0x00b62ef9 simple_transaction_read vmlinux EXPORT_SYMBOL
@@ -2367,6 +2338,7 @@
0x582acae6 generic_getxattr vmlinux EXPORT_SYMBOL
0xd27b805b gss_mech_register net/sunrpc/auth_gss/auth_rpcgss
EXPORT_SYMBOL
0x9f3e766c mpage_readpages vmlinux EXPORT_SYMBOL
+0x5063f375 iscsi_conn_get_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xc3025078 saa7146_pgtable_free drivers/media/common/saa7146
EXPORT_SYMBOL_GPL
0xb758b225 acpi_disable_event vmlinux EXPORT_SYMBOL
0x6915c91c pci_request_regions vmlinux EXPORT_SYMBOL
@@ -2415,6 +2387,7 @@
0xdb6d5cb7 ip_nat_seq_adjust net/ipv4/netfilter/ip_nat
EXPORT_SYMBOL
0x7594e7e6 ip_nat_pptp_hook_outbound
net/ipv4/netfilter/ip_conntrack_pptp EXPORT_SYMBOL
0x97f72823 fat_attach fs/fat/fat EXPORT_SYMBOL_GPL
+0x5df3cb80 iscsi_pool_free drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x943b80a3 ip_mc_inc_group vmlinux EXPORT_SYMBOL
0x71196147 tcp_orphan_count vmlinux EXPORT_SYMBOL_GPL
0xcdc39f97 request_key_with_auxdata vmlinux EXPORT_SYMBOL
@@ -2431,6 +2404,7 @@
0xa1c6041d ata_scsi_simulate drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x43c17b60 __bread vmlinux EXPORT_SYMBOL
0xeb134d83 hrtimer_init vmlinux EXPORT_SYMBOL_GPL
+0x93fa7c8b iscsi_session_teardown drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x4c0b0237 ds1337_do_command drivers/i2c/chips/ds1337
EXPORT_SYMBOL_GPL
0x9ceb163c memcpy_toiovec vmlinux EXPORT_SYMBOL
0x4b085dbf agp3_generic_configure vmlinux EXPORT_SYMBOL
@@ -2534,6 +2508,7 @@
0x48232e0f tipc_forward_buf2name net/tipc/tipc EXPORT_SYMBOL
0x0b350527 hci_suspend_dev net/bluetooth/bluetooth EXPORT_SYMBOL
0x6b0b234e vcc_release_async net/atm/atm EXPORT_SYMBOL
+0x2add700b iscsi_conn_error
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd57ab9d4 tcp_v4_send_check vmlinux EXPORT_SYMBOL
0xcd28f422 dev_close vmlinux EXPORT_SYMBOL
0x55db1086 isa_bridge vmlinux EXPORT_SYMBOL
@@ -2580,12 +2555,14 @@
0x191125b2 nr_mce_banks vmlinux EXPORT_SYMBOL_GPL
0xdf5008fc tipc_peer net/tipc/tipc EXPORT_SYMBOL
0x3c102da1 ip_conntrack_expect_alloc
net/ipv4/netfilter/ip_conntrack EXPORT_SYMBOL
+0x1613f701 iscsi_create_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x335d4099 journal_get_create_access fs/jbd/jbd
EXPORT_SYMBOL
0xe446fdd5 ib_flush_fmr_pool drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0xfba57f51 hpsb_speedto_str drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0x7c2ca2de secure_tcpv6_sequence_number vmlinux EXPORT_SYMBOL
0xfb86b96f dlm_errname fs/ocfs2/dlm/ocfs2_dlm
EXPORT_SYMBOL_GPL
0x7882b4b1 __fscache_register_netfs fs/fscache/fscache
EXPORT_SYMBOL
+0xbc11bbc3 iscsi_eh_abort drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x83e5c3a2 cx8802_fini_common drivers/media/video/cx88/cx8802
EXPORT_SYMBOL
0x9ef1615c request_key vmlinux EXPORT_SYMBOL
0x87c7272f __fscache_read_or_alloc_pages fs/fscache/fscache
EXPORT_SYMBOL
@@ -2597,6 +2574,7 @@
0x2b02b3f5 hpsb_get_tlabel drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xe63ba0b4 pci_do_scan_bus vmlinux EXPORT_SYMBOL
0x55097d3b bt_sock_unlink net/bluetooth/bluetooth EXPORT_SYMBOL
+0xf040633b iscsi_add_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x4a368ee3 ves1x93_attach drivers/media/dvb/frontends/ves1x93
EXPORT_SYMBOL
0x224f1c76 ide_register_hw_with_fixup vmlinux EXPORT_SYMBOL
0x1dcaa0c8 v4l2_prio_max drivers/media/video/v4l2-common
EXPORT_SYMBOL
@@ -2608,6 +2586,7 @@
0x52524a17 hpsb_iso_recv_unlisten_channel
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x2faa8ef9 usb_hcd_resume_root_hub vmlinux EXPORT_SYMBOL_GPL
0x98427c58 securityfs_remove vmlinux EXPORT_SYMBOL_GPL
+0x71b9b5e8 iscsi_check_assign_cmdsn drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xcc28624a hostap_set_string
drivers/net/wireless/hostap/hostap EXPORT_SYMBOL
0x437749bf videobuf_mmap_setup drivers/media/video/video-buf
EXPORT_SYMBOL_GPL
0x734e083f tpm_calc_ordinal_duration drivers/char/tpm/tpm
EXPORT_SYMBOL_GPL
@@ -2639,6 +2618,7 @@
0xfc7476fb dvb_pll_microtune_4042
drivers/media/dvb/frontends/dvb-pll EXPORT_SYMBOL
0x30bfe0e0 kmap_high vmlinux EXPORT_SYMBOL
0x79ad224b tasklet_kill vmlinux EXPORT_SYMBOL
+0xcefc5fbb iscsi_if_destroy_session_done
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x009072b2 scsi_print_command drivers/scsi/scsi_mod
EXPORT_SYMBOL
0xeb424b8f dvb_unregister_frontend
drivers/media/dvb/dvb-core/dvb-core EXPORT_SYMBOL
0xd4030763 __gameport_register_port
drivers/input/gameport/gameport EXPORT_SYMBOL
@@ -2651,6 +2631,7 @@
0x84be96bb sk_stop_timer vmlinux EXPORT_SYMBOL
0x94aac529 pcmcia_register_driver vmlinux EXPORT_SYMBOL
0x00d7f04d locks_remove_posix vmlinux EXPORT_SYMBOL
+0x08674e01 iscsi_unregister_transport
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x60769d88 pcie_port_service_unregister vmlinux EXPORT_SYMBOL
0x103aa537 radix_tree_delete vmlinux EXPORT_SYMBOL
0x9320ec72 dm_table_flush_all drivers/md/dm-mod
EXPORT_SYMBOL
@@ -2845,6 +2826,7 @@
0x1e6d26a8 strstr vmlinux EXPORT_SYMBOL
0x794487ee disable_hlt vmlinux EXPORT_SYMBOL
0xf890fe7f pm_idle vmlinux EXPORT_SYMBOL
+0xad53bc76 iscsi_prep_scsi_cmd_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x285dfffe mpt_proc_root_dir drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x447ec1bc cx24110_pll_write
drivers/media/dvb/frontends/cx24110 EXPORT_SYMBOL
0x312e5334 k8_northbridges vmlinux EXPORT_SYMBOL
@@ -2886,6 +2868,7 @@
0xf8c5cdec d_alloc_anon vmlinux EXPORT_SYMBOL
0x6f2e907f copy_strings_kernel vmlinux EXPORT_SYMBOL
0x916bad0d __wait_on_bit vmlinux EXPORT_SYMBOL
+0xce7cf8ca iscsi_recv_pdu drivers/scsi/scsi_transport_iscsi
EXPORT_SYMBOL_GPL
0x04403fcf unregister_capi_driver drivers/isdn/capi/kernelcapi
EXPORT_SYMBOL
0x20645642 drm_debug drivers/char/drm/drm EXPORT_SYMBOL
0xac7d087b led_trigger_register_simple vmlinux
EXPORT_SYMBOL_GPL
@@ -3008,6 +2991,7 @@
0xaeea0069 acpi_run_oshp vmlinux EXPORT_SYMBOL_GPL
0x4f2cd6e8 snd_cs4231_info_double sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0x0e9e79d5 xdr_encode_opaque net/sunrpc/sunrpc
EXPORT_SYMBOL
+0xf640e867 iscsi_session_recovery_timedout drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xe6dbcd72 rtc_class_close drivers/rtc/rtc-core
EXPORT_SYMBOL_GPL
0x7b5d4b7a ib_is_mad_class_rmpp drivers/infiniband/core/ib_mad
EXPORT_SYMBOL
0x05949c77 snd_timer_global_unregister sound/core/snd-timer
EXPORT_SYMBOL
@@ -3113,6 +3097,7 @@
0x107d6ba3 __get_free_pages vmlinux EXPORT_SYMBOL
0xcb216f1e find_task_by_pid_type vmlinux EXPORT_SYMBOL
0xbb189cad disallow_signal vmlinux EXPORT_SYMBOL
+0xe71028ea iscsi_pool_init drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xdbcd416e sysctl_ip_nonlocal_bind vmlinux EXPORT_SYMBOL
0xeedd9ef6 pciserial_init_ports vmlinux EXPORT_SYMBOL_GPL
0x3b131d8d matroxfb_g450_shutdown
drivers/video/matrox/matroxfb_g450 EXPORT_SYMBOL
@@ -3148,6 +3133,7 @@
0x540f9040 acpi_os_sleep vmlinux EXPORT_SYMBOL
0x3d0dfdea vfs_rename vmlinux EXPORT_SYMBOL
0x5497aa2d generic_ro_fops vmlinux EXPORT_SYMBOL
+0x09adf54c iscsi_free_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xb819e673 hpsb_set_hostinfo drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xa29b16c9 kthread_bind vmlinux EXPORT_SYMBOL
0x833a3e07 snd_midi_channel_set_clear
sound/core/seq/snd-seq-midi-emul EXPORT_SYMBOL
@@ -3385,6 +3371,7 @@
0x56eea045 fb_blank vmlinux EXPORT_SYMBOL
0x4ddc4b9f utf8_mbtowc vmlinux EXPORT_SYMBOL
0x51a880ca open_exec vmlinux EXPORT_SYMBOL
+0x54efe73e iscsi_remove_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x53854e7d acpi_initialize_subsystem vmlinux EXPORT_SYMBOL
0xb80d62df mb_cache_entry_find_next vmlinux EXPORT_SYMBOL
0x656d7190 ip_vs_skb_replace net/ipv4/ipvs/ip_vs
EXPORT_SYMBOL
@@ -3406,6 +3393,7 @@
0xf4965aaf qdisc_lock_tree vmlinux EXPORT_SYMBOL
0x9ceca2f1 mempool_create_node vmlinux EXPORT_SYMBOL
0x4958824b scsi_bios_ptable drivers/scsi/scsi_mod
EXPORT_SYMBOL
+0xa1418b12 iscsi_verify_itt drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x3074f033 drm_order drivers/char/drm/drm EXPORT_SYMBOL
0xbfb37234 dev_set_promiscuity vmlinux EXPORT_SYMBOL
0xe7ecaf45 snd_mpu401_uart_interrupt
sound/drivers/mpu401/snd-mpu401-uart EXPORT_SYMBOL
@@ -3482,6 +3470,7 @@
0xf9448805 seq_path vmlinux EXPORT_SYMBOL
0xcc5005fe msleep_interruptible vmlinux EXPORT_SYMBOL
0xf8b2ff6e g_verify_token_header net/sunrpc/auth_gss/auth_rpcgss
EXPORT_SYMBOL
+0x02ae6629 iscsi_session_setup drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf5767401 hpsb_update_config_rom drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0x65414e67 dev_valid_name vmlinux EXPORT_SYMBOL
0x3be89d3c usb_register_notify vmlinux EXPORT_SYMBOL_GPL
@@ -4041,6 +4030,7 @@
0xe61b6e89 generic_listxattr vmlinux EXPORT_SYMBOL
0x5bc201be kmem_cache_zalloc vmlinux EXPORT_SYMBOL
0xff2193fa ieee80211softmac_start
net/ieee80211/softmac/ieee80211softmac EXPORT_SYMBOL_GPL
+0xb31cb3ec iscsi_prep_unsolicit_data_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x67e33bda mptscsih_io_done drivers/message/fusion/mptscsih
EXPORT_SYMBOL
0xf1490f9a csr1212_release_keyval drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xf6ebc03b net_ratelimit vmlinux EXPORT_SYMBOL
@@ -4100,6 +4090,7 @@
0xfcec0987 enable_irq vmlinux EXPORT_SYMBOL
0x1e7bbcb3 kernel_restart vmlinux EXPORT_SYMBOL_GPL
0x9c7077bd enable_hlt vmlinux EXPORT_SYMBOL
+0x3c85f0a3 iscsi_set_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xce7e0ce2 sata_phy_resume drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x8b9999be bt878_device_control drivers/media/dvb/bt8xx/bt878
EXPORT_SYMBOL
0x43837ebc b1_getrevision drivers/isdn/hardware/avm/b1
EXPORT_SYMBOL
@@ -4142,6 +4133,7 @@
0x50679ae0 FsmRestartTimer drivers/isdn/hisax/hisax
EXPORT_SYMBOL
0xc31f224a gameport_unregister_port
drivers/input/gameport/gameport EXPORT_SYMBOL
0xa0d95792 ip_route_input vmlinux EXPORT_SYMBOL
+0x738899f9 iscsi_conn_teardown drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x80e66d5a device_remove_file vmlinux EXPORT_SYMBOL_GPL
0xbf19c9c8 hpsb_allocate_and_register_addrspace
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x29c14226 ipv6_skip_exthdr vmlinux EXPORT_SYMBOL
@@ -4691,6 +4683,7 @@
0x9cbe4d8f ib_create_cm_id drivers/infiniband/core/ib_cm
EXPORT_SYMBOL
0xf338d4c3 netlink_unregister_notifier vmlinux EXPORT_SYMBOL
0x04104e78 simple_release_fs vmlinux EXPORT_SYMBOL
+0x7452449d iscsi_change_queue_depth drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xb189a6d9 ipmi_create_user
drivers/char/ipmi/ipmi_msghandler EXPORT_SYMBOL
0x500145db generic_file_aio_write_nolock vmlinux EXPORT_SYMBOL
0xcef7cefe scsi_host_put drivers/scsi/scsi_mod EXPORT_SYMBOL
@@ -4879,6 +4872,7 @@
0x243d71d6 generic_write_checks vmlinux EXPORT_SYMBOL
0xd6035d05 do_settimeofday vmlinux EXPORT_SYMBOL
0x72270e35 do_gettimeofday vmlinux EXPORT_SYMBOL
+0x7d88a1fb iscsi_session_get_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x68ef30a6 uart_match_port vmlinux EXPORT_SYMBOL
0x36d5355b acpi_register_gsi vmlinux EXPORT_SYMBOL
0xf8962595 destroy_8023_client net/802/p8023 EXPORT_SYMBOL
@@ -5083,6 +5077,7 @@
0xc55f528f usb_sg_cancel vmlinux EXPORT_SYMBOL
0x25740865 struct_module vmlinux EXPORT_SYMBOL
0x0f2103ff snd_emux_new sound/synth/emux/snd-emux-synth
EXPORT_SYMBOL
+0xfd9f41f8 iscsi_destroy_conn
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x9f07a59b ib_register_device drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0x6d41d8df nf_register_queue_handler vmlinux EXPORT_SYMBOL
0x5fb31e7e pcmcia_get_status vmlinux EXPORT_SYMBOL
@@ -5140,6 +5135,7 @@
0xd381cfa5 usb_driver_claim_interface vmlinux EXPORT_SYMBOL
0x01139ffc max_mapnr vmlinux EXPORT_SYMBOL
0xb24aa0ed snd_opl3_reset sound/drivers/opl3/snd-opl3-lib
EXPORT_SYMBOL
+0x9ede8aa5 iscsi_conn_failure drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x865e1b56 dvb_pll_lg_z201 drivers/media/dvb/frontends/dvb-pll
EXPORT_SYMBOL
0x368518de led_trigger_set vmlinux EXPORT_SYMBOL_GPL
0x07e93cdc snd_pcm_mmap_data sound/core/snd-pcm
EXPORT_SYMBOL
@@ -5270,6 +5266,7 @@
0xe535efb8 cdrom_mode_sense drivers/cdrom/cdrom
EXPORT_SYMBOL
0xf4f52f93 dqstats vmlinux EXPORT_SYMBOL
0x9a6ea734 mb_cache_entry_release vmlinux EXPORT_SYMBOL
+0x3340bfd1 iscsi_conn_send_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd45b5eb5 capi_cmsg2str drivers/isdn/capi/kernelcapi
EXPORT_SYMBOL
0xa6bda823 ib_query_qp drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0x8df296f8 snd_ak4531_suspend sound/pci/ac97/snd-ak4531-codec
EXPORT_SYMBOL
@@ -5449,6 +5446,7 @@
0x1eb922a3 IO_APIC_get_PCI_irq_vector vmlinux EXPORT_SYMBOL
0x30f23b16 snd_cs4236_ext_out sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0xb70fbe06 nfs4_acl_free fs/nfsd/nfsd EXPORT_SYMBOL
+0xf53fce1c iscsi_register_transport
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x1a12dda7 netlink_ack vmlinux EXPORT_SYMBOL
0x397b8738 sock_no_bind vmlinux EXPORT_SYMBOL
0x8335ce68 sock_get_timestamp vmlinux EXPORT_SYMBOL
@@ -5505,6 +5503,7 @@
0xd60ded4d bus_unregister vmlinux EXPORT_SYMBOL_GPL
0x69b7b928 __elv_add_request vmlinux EXPORT_SYMBOL
0x604a58fd set_bh_page vmlinux EXPORT_SYMBOL
+0x7fb2d2c4 iscsi_if_create_session_done
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd38d8ae2 hermes_read_ltv drivers/net/wireless/hermes
EXPORT_SYMBOL
0x28402f7c cx8802_resume_common drivers/media/video/cx88/cx8802
EXPORT_SYMBOL
0xa0e26709 parport_ieee1284_read_byte drivers/parport/parport
EXPORT_SYMBOL
@@ -5618,6 +5617,7 @@
0x4d6908b2 _atomic_dec_and_lock vmlinux EXPORT_SYMBOL
0xea7987f1 key_update vmlinux EXPORT_SYMBOL
0xe8b4c87c simple_prepare_write vmlinux EXPORT_SYMBOL
+0x71a7d5f6 iscsi_conn_bind drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x129ec2d2 xfrm_register_km vmlinux EXPORT_SYMBOL
0x57b8433a ip_mc_dec_group vmlinux EXPORT_SYMBOL
0xcb7131fb fb_get_options vmlinux EXPORT_SYMBOL
Erez Zilber
> Anyway removing and re-installing kernel-devel gives me back the
> original Modules.symvers.
> I reinstalled again open-iscsi, did a depmod -aq, run your script and
> made a diff between the original Modules.symvers and the newly
> generated one. Here's the diff (-ruN format):
>
> --- Module.symvers 2006-10-29 17:58:46.000000000 +0100
> +++ Module.symvers.org 2006-10-29 17:53:15.000000000 +0100
> @@ -1,45 +1,3 @@
> -0x class_to_transport_session libiscsi
> -0x iscsi_change_queue_depth libiscsi
> -0x iscsi_check_assign_cmdsn libiscsi
> -0x __iscsi_complete_pdu libiscsi
> -0x iscsi_complete_pdu libiscsi
> -0x iscsi_conn_bind libiscsi
> -0x iscsi_conn_failure libiscsi
> -0x iscsi_conn_get_param libiscsi
> -0x iscsi_conn_send_pdu libiscsi
> -0x iscsi_conn_setup libiscsi
>
may require small fixes). It replaced the version number with 0x (which
is wrong). It should have replaced it with the new version. The 2nd
problem is that it replaced drivers/scsi/libiscsi with libiscsi. I guess
that these can be easily fixed. However, I don't have time to do that at
the moment.
Erez
Albert Pauw
> may require small fixes). It replaced the version number with 0x (which
> is wrong). It should have replaced it with the new version. The 2nd
> problem is that it replaced drivers/scsi/libiscsi with libiscsi. I guess
> that these can be easily fixed. However, I don't have time to do that at
> the moment
Thanks Erez,
the second problem is explainable. I ran the script out of the kernel
directory of the open-iscsi source tree.
So it would find the (three) kernel modules without a search path.
Erez Zilber
I'm currently out of the office (until next week), so I will try to do my best without being able to run anything.
About the 2nd problem - if you run it from open-iscsi/kernel, does it work ok?
Can you say anything about the cause for the 1st problem?
Erez
Albert Pauw
Here's the modified version:
> #!/bin/bash
> SYMS_FILE=/tmp/syms
>
> MODULE_NAMES="iscsi_tcp.ko libiscsi.ko scsi_transport_iscsi.ko"
>
> rm -f $SYMS_FILE
>
> n_mods=0
>
> cd /lib/modules/`uname -r`/kernel
> for mod in $MODULE_NAMES ; do
> nm -o drivers/scsi/$mod |grep __crc >> $SYMS_FILE
> n_mods=$((n_mods+1))
> done
>
> n_syms=$(wc -l $SYMS_FILE |cut -f1 -d" ")
> echo found $n_syms open-iscsi symbols in $n_mods open-iscsi modules
> n=1
>
> MOD_SYMVERS_OPEN_ISCSI=/tmp/Module.symvers.open-iscsi
> MOD_SYMVERS_PATCH=/tmp/Module.symvers.patch
> if [ -f /lib/modules/`uname -r`/source/Module.symvers ] ; then
> MOD_SYMVERS_KERNEL=/lib/modules/`uname -r`/source/Module.symvers
> elif [ -f /lib/modules/`uname -r`/build/Module.symvers ] ; then
> MOD_SYMVERS_KERNEL=/lib/modules/`uname -r`/build/Module.symvers
> else
> echo file Module.symvers not found
> fi
>
> if [ ! -z $MOD_SYMVERS_KERNEL ] ; then
>
> rm -f $MOD_SYMVERS_OPEN_ISCSI
>
> while [ $n -le $n_syms ] ; do
> line=$(head -$n $SYMS_FILE |tail -1)
> mod_path=$(echo $line|cut -f1 -d:)
> symbol_crc=$(echo $line|cut -f2 -d:)
> crc=$(echo $symbol_crc|cut -f1 -d" ")
> sym=$(echo $symbol_crc|cut -f3 -d" ")
> sym=${sym:6}
> echo -e "0x$crc\t$sym\t$mod_path" >> $MOD_SYMVERS_OPEN_ISCSI
> if [ -z $allsyms ] ; then
> allsyms=$sym
> else
> allsyms="$allsyms|$sym"
> fi
> n=$((n+1))
> done
>
> egrep -v "$allsyms" $MOD_SYMVERS_KERNEL >> $MOD_SYMVERS_OPEN_ISCSI
> diff -u $MOD_SYMVERS_KERNEL $MOD_SYMVERS_OPEN_ISCSI > $MOD_SYMVERS_PATCH patch -d $(dirname $MOD_SYMVERS_KERNEL) < $MOD_SYMVERS_PATCH
> fi
Now, when I am running this, I get:
found 42 open-iscsi symbols in 3 open-iscsi modules
patching file Module.symvers
Here is the diff between the original Module.symvers and the modified
one:
--- Module.symvers.org 2006-10-29 17:53:15.000000000 +0100
+++ Module.symvers 2006-10-31 18:36:44.000000000 +0100
@@ -1,3 +1,45 @@
+0x8829b2c3 class_to_transport_session
drivers/scsi/libiscsi.ko
+0x7452449d iscsi_change_queue_depth
drivers/scsi/libiscsi.ko
+0x5252c534 iscsi_check_assign_cmdsn
drivers/scsi/libiscsi.ko
+0xc7d65656 __iscsi_complete_pdu drivers/scsi/libiscsi.ko
+0x9efdf951 iscsi_complete_pdu drivers/scsi/libiscsi.ko
+0xb8528221 iscsi_conn_bind drivers/scsi/libiscsi.ko
+0xa1a1abcb iscsi_conn_failure drivers/scsi/libiscsi.ko
+0x47580196 iscsi_conn_get_param drivers/scsi/libiscsi.ko
+0x047f7b4a iscsi_conn_send_pdu drivers/scsi/libiscsi.ko
+0x461cb302 iscsi_conn_setup drivers/scsi/libiscsi.ko
+0xd6316a68 iscsi_conn_start drivers/scsi/libiscsi.ko
+0x57171366 iscsi_conn_stop drivers/scsi/libiscsi.ko
+0xfbe923d2 iscsi_conn_teardown drivers/scsi/libiscsi.ko
+0xbc11bbc3 iscsi_eh_abort drivers/scsi/libiscsi.ko
+0xf89a0abd iscsi_eh_host_reset drivers/scsi/libiscsi.ko
+0x5df3cb80 iscsi_pool_free drivers/scsi/libiscsi.ko
+0xe71028ea iscsi_pool_init drivers/scsi/libiscsi.ko
+0x60b5118e iscsi_prep_scsi_cmd_pdu drivers/scsi/libiscsi.ko
+0x0db777cf iscsi_prep_unsolicit_data_pdu
drivers/scsi/libiscsi.ko
+0xb98bbbfb iscsi_queuecommand drivers/scsi/libiscsi.ko
+0xca5a2f62 iscsi_session_get_param drivers/scsi/libiscsi.ko
+0x5a12ad76 iscsi_session_recovery_timedout
drivers/scsi/libiscsi.ko
+0x112ec66a iscsi_session_setup drivers/scsi/libiscsi.ko
+0x2e9ccb24 iscsi_session_teardown drivers/scsi/libiscsi.ko
+0x18532f2d iscsi_set_param drivers/scsi/libiscsi.ko
+0x760e7906 iscsi_verify_itt drivers/scsi/libiscsi.ko
+0x4f366286 iscsi_add_session
drivers/scsi/scsi_transport_iscsi.ko
+0x341af46e iscsi_alloc_session
drivers/scsi/scsi_transport_iscsi.ko
+0xade24689 iscsi_block_session
drivers/scsi/scsi_transport_iscsi.ko
+0xba2c1b24 iscsi_conn_error
drivers/scsi/scsi_transport_iscsi.ko
+0xaf76abe0 iscsi_create_conn
drivers/scsi/scsi_transport_iscsi.ko
+0x7fadb3bf iscsi_create_session
drivers/scsi/scsi_transport_iscsi.ko
+0x2a1da671 iscsi_destroy_conn
drivers/scsi/scsi_transport_iscsi.ko
+0xf67dc54d iscsi_destroy_session
drivers/scsi/scsi_transport_iscsi.ko
+0x0181abc9 iscsi_free_session
drivers/scsi/scsi_transport_iscsi.ko
+0x069f4102 iscsi_if_create_session_done
drivers/scsi/scsi_transport_iscsi.ko
+0x557267d5 iscsi_if_destroy_session_done
drivers/scsi/scsi_transport_iscsi.ko
+0x7706d548 iscsi_recv_pdu drivers/scsi/scsi_transport_iscsi.ko
+0x2d51e623 iscsi_register_transport
drivers/scsi/scsi_transport_iscsi.ko
+0xb31c80bf iscsi_remove_session
drivers/scsi/scsi_transport_iscsi.ko
+0xb1daa093 iscsi_unblock_session
drivers/scsi/scsi_transport_iscsi.ko
+0xbc80e222 iscsi_unregister_transport
drivers/scsi/scsi_transport_iscsi.ko
0x88b73627 tipc_get_addr net/tipc/tipc EXPORT_SYMBOL
0x6fb5ab71 mpt_deregister drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x4266f38c firmware_unregister vmlinux EXPORT_SYMBOL_GPL
@@ -66,7 +108,6 @@
0x347a20b7 dvb_pll_philips_sd1878_tda8261
drivers/media/dvb/frontends/dvb-pll EXPORT_SYMBOL
0xf6e19955 transport_class_register vmlinux
EXPORT_SYMBOL_GPL
0x2f85bbbe snd_emux_terminate_all sound/synth/emux/snd-emux-synth
EXPORT_SYMBOL
-0x2f1913dc iscsi_conn_setup drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x4459fd47 mpt_free_fw_memory drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x53928019 dm_put_device drivers/md/dm-mod EXPORT_SYMBOL
0xee1b7bd4 dm_get_device drivers/md/dm-mod EXPORT_SYMBOL
@@ -906,7 +947,6 @@
0x5b49d5ce nobh_commit_write vmlinux EXPORT_SYMBOL
0x3ed5142b ip_ct_iterate_cleanup net/ipv4/netfilter/ip_conntrack
EXPORT_SYMBOL
0x2be5133a scsi_is_sdev_device drivers/scsi/scsi_mod
EXPORT_SYMBOL
-0x77cfc2dd class_to_transport_session drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd15db3dd sk_free vmlinux EXPORT_SYMBOL
0x02cd3086 __down_failed_trylock vmlinux EXPORT_SYMBOL
0x28c68196 ieee80211softmac_notify_gfp
net/ieee80211/softmac/ieee80211softmac EXPORT_SYMBOL_GPL
@@ -1039,7 +1079,6 @@
0x84e531af iput vmlinux EXPORT_SYMBOL
0xd072a79c sleep_on_timeout vmlinux EXPORT_SYMBOL
0x5a157ae4 nfs4_acl_get_whotype fs/nfsd/nfsd EXPORT_SYMBOL
-0xbd95d973 iscsi_alloc_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x8f18b846 cx88_shutdown drivers/media/video/cx88/cx88xx
EXPORT_SYMBOL
0xd96bca50 hpsb_packet_sent drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xebf91792 create_proc_entry vmlinux EXPORT_SYMBOL
@@ -1053,7 +1092,6 @@
0x7aa4ff90 neigh_event_ns vmlinux EXPORT_SYMBOL
0xd5e1f1a4 fb_firmware_edid vmlinux EXPORT_SYMBOL
0x01ac0524 key_negate_and_link vmlinux EXPORT_SYMBOL
-0xb98bbbfb iscsi_queuecommand drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x85839d63 hpsb_unregister_highlevel
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x88ee4764 request_firmware_nowait vmlinux EXPORT_SYMBOL
0xd08197fa acpi_load_tables vmlinux EXPORT_SYMBOL
@@ -1200,7 +1238,6 @@
0xe8cb825f complete vmlinux EXPORT_SYMBOL
0xb703874c snd_hda_bus_new sound/pci/hda/snd-hda-codec
EXPORT_SYMBOL
0xf81a8679 config_item_init_type_name fs/configfs/configfs
EXPORT_SYMBOL
-0xe314f4f9 iscsi_block_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x02ba2212 ata_port_freeze drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x5b9da9ae ata_bmdma_start drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x6ade8b24 __gameport_register_driver
drivers/input/gameport/gameport EXPORT_SYMBOL
@@ -1257,7 +1294,6 @@
0xaaa1d535 inet_dgram_connect vmlinux EXPORT_SYMBOL
0xff56c944 driver_unregister vmlinux EXPORT_SYMBOL_GPL
0x2b5311e6 end_that_request_first vmlinux EXPORT_SYMBOL
-0x78ff005a iscsi_unblock_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x5ebefe4b v4l_printk_ioctl drivers/media/video/v4l2-common
EXPORT_SYMBOL
0xe3cd9b5c saa7146_debug drivers/media/common/saa7146
EXPORT_SYMBOL_GPL
0xac6acb48 kobject_put vmlinux EXPORT_SYMBOL
@@ -1381,7 +1417,6 @@
0x87754115 raw_notifier_chain_register vmlinux
EXPORT_SYMBOL_GPL
0x6b5e3f2c snd_midi_event_decode
sound/core/seq/snd-seq-midi-event EXPORT_SYMBOL
0x2ae981ab scsi_host_alloc drivers/scsi/scsi_mod EXPORT_SYMBOL
-0xf89a0abd iscsi_eh_host_reset drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf7c5f008 cdrom_get_media_event drivers/cdrom/cdrom
EXPORT_SYMBOL
0xcffb4fb8 pcmcia_get_configuration_info vmlinux EXPORT_SYMBOL
0x79e4fd48 sysfs_remove_file vmlinux EXPORT_SYMBOL_GPL
@@ -1553,7 +1588,6 @@
0x7372acdc cpufreq_cpu_get vmlinux EXPORT_SYMBOL_GPL
0xba8d1777 free_buffer_head vmlinux EXPORT_SYMBOL
0x9e4a7595 fget vmlinux EXPORT_SYMBOL
-0x398d20f8 iscsi_complete_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf71f5871 phy_sanitize_settings drivers/net/phy/libphy
EXPORT_SYMBOL
0x62c4760f ide_config_drive_speed vmlinux EXPORT_SYMBOL
0x2dd1d503 rdc_8820_reset drivers/media/dvb/bt8xx/dst
EXPORT_SYMBOL
@@ -1633,7 +1667,6 @@
0xa5c79544 switch_APIC_timer_to_ipi vmlinux EXPORT_SYMBOL
0x5426a49a snd_cs4231_mce_down sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0xfdc1b546 cache_check net/sunrpc/sunrpc EXPORT_SYMBOL
-0x28eedccb iscsi_destroy_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd32b89e3 video_usercopy drivers/media/video/videodev
EXPORT_SYMBOL
0x5dbaffb1 usb_check_bandwidth vmlinux EXPORT_SYMBOL
0x01438985 acpi_fadt_is_v1 vmlinux EXPORT_SYMBOL
@@ -1858,7 +1891,6 @@
0x0a7a2ab5 snd_card_file_remove sound/core/snd EXPORT_SYMBOL
0x3b91f3af snd_free_pages sound/core/snd-page-alloc
EXPORT_SYMBOL
0x1432a31b o2nm_get_node_by_num
fs/ocfs2/cluster/ocfs2_nodemanager EXPORT_SYMBOL_GPL
-0x1aac80db __iscsi_complete_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x858136e4 usb_init_urb vmlinux EXPORT_SYMBOL
0x85e5a3db ktime_get_ts vmlinux EXPORT_SYMBOL_GPL
0x5a4896a8 __put_user_2 vmlinux EXPORT_SYMBOL
@@ -2012,7 +2044,6 @@
0x7ddcee1c inet_dccp_listen net/dccp/dccp
EXPORT_SYMBOL_GPL
0x688c7ce0 irda_register_dongle drivers/net/irda/sir-dev
EXPORT_SYMBOL
0x263b54cc acpi_resource_to_address64 vmlinux EXPORT_SYMBOL
-0xdb016841 iscsi_conn_stop drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x25a7ebdf proc_dointvec_minmax vmlinux EXPORT_SYMBOL
0x3c9435bf atm_charge net/atm/atm EXPORT_SYMBOL
0x3811daea ir_codes_manli drivers/media/common/ir-common
EXPORT_SYMBOL_GPL
@@ -2045,7 +2076,6 @@
0x76670e30 snd_vx_check_reg_bit sound/drivers/vx/snd-vx-lib
EXPORT_SYMBOL
0xd93f48d8 snd_seq_instr_free_use sound/core/seq/snd-seq-instr
EXPORT_SYMBOL
0xbaeb4700 o2hb_check_node_heartbeating_from_callback
fs/ocfs2/cluster/ocfs2_nodemanager EXPORT_SYMBOL_GPL
-0x311e4995 iscsi_conn_start drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd8b1bf0c ethtool_op_set_tx_hw_csum vmlinux EXPORT_SYMBOL
0x2ea16d99 end_that_request_chunk vmlinux EXPORT_SYMBOL
0x6ba6444c dvb_ringbuffer_pkt_write
drivers/media/dvb/dvb-core/dvb-core EXPORT_SYMBOL
@@ -2323,7 +2353,6 @@
0x7f0d89cc gigaset_freedriver drivers/isdn/gigaset/gigaset
EXPORT_SYMBOL_GPL
0x23679939 __iowrite32_copy vmlinux EXPORT_SYMBOL_GPL
0x7149979e xdr_enter_page net/sunrpc/sunrpc EXPORT_SYMBOL
-0xadd2f52f iscsi_create_conn
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x647b4230 ata_do_eh drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x612390ad netpoll_set_trap vmlinux EXPORT_SYMBOL
0x00b62ef9 simple_transaction_read vmlinux EXPORT_SYMBOL
@@ -2338,7 +2367,6 @@
0x582acae6 generic_getxattr vmlinux EXPORT_SYMBOL
0xd27b805b gss_mech_register net/sunrpc/auth_gss/auth_rpcgss
EXPORT_SYMBOL
0x9f3e766c mpage_readpages vmlinux EXPORT_SYMBOL
-0x5063f375 iscsi_conn_get_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xc3025078 saa7146_pgtable_free drivers/media/common/saa7146
EXPORT_SYMBOL_GPL
0xb758b225 acpi_disable_event vmlinux EXPORT_SYMBOL
0x6915c91c pci_request_regions vmlinux EXPORT_SYMBOL
@@ -2387,7 +2415,6 @@
0xdb6d5cb7 ip_nat_seq_adjust net/ipv4/netfilter/ip_nat
EXPORT_SYMBOL
0x7594e7e6 ip_nat_pptp_hook_outbound
net/ipv4/netfilter/ip_conntrack_pptp EXPORT_SYMBOL
0x97f72823 fat_attach fs/fat/fat EXPORT_SYMBOL_GPL
-0x5df3cb80 iscsi_pool_free drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x943b80a3 ip_mc_inc_group vmlinux EXPORT_SYMBOL
0x71196147 tcp_orphan_count vmlinux EXPORT_SYMBOL_GPL
0xcdc39f97 request_key_with_auxdata vmlinux EXPORT_SYMBOL
@@ -2404,7 +2431,6 @@
0xa1c6041d ata_scsi_simulate drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x43c17b60 __bread vmlinux EXPORT_SYMBOL
0xeb134d83 hrtimer_init vmlinux EXPORT_SYMBOL_GPL
-0x93fa7c8b iscsi_session_teardown drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x4c0b0237 ds1337_do_command drivers/i2c/chips/ds1337
EXPORT_SYMBOL_GPL
0x9ceb163c memcpy_toiovec vmlinux EXPORT_SYMBOL
0x4b085dbf agp3_generic_configure vmlinux EXPORT_SYMBOL
@@ -2508,7 +2534,6 @@
0x48232e0f tipc_forward_buf2name net/tipc/tipc EXPORT_SYMBOL
0x0b350527 hci_suspend_dev net/bluetooth/bluetooth EXPORT_SYMBOL
0x6b0b234e vcc_release_async net/atm/atm EXPORT_SYMBOL
-0x2add700b iscsi_conn_error
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd57ab9d4 tcp_v4_send_check vmlinux EXPORT_SYMBOL
0xcd28f422 dev_close vmlinux EXPORT_SYMBOL
0x55db1086 isa_bridge vmlinux EXPORT_SYMBOL
@@ -2555,14 +2580,12 @@
0x191125b2 nr_mce_banks vmlinux EXPORT_SYMBOL_GPL
0xdf5008fc tipc_peer net/tipc/tipc EXPORT_SYMBOL
0x3c102da1 ip_conntrack_expect_alloc
net/ipv4/netfilter/ip_conntrack EXPORT_SYMBOL
-0x1613f701 iscsi_create_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x335d4099 journal_get_create_access fs/jbd/jbd
EXPORT_SYMBOL
0xe446fdd5 ib_flush_fmr_pool drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0xfba57f51 hpsb_speedto_str drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0x7c2ca2de secure_tcpv6_sequence_number vmlinux EXPORT_SYMBOL
0xfb86b96f dlm_errname fs/ocfs2/dlm/ocfs2_dlm
EXPORT_SYMBOL_GPL
0x7882b4b1 __fscache_register_netfs fs/fscache/fscache
EXPORT_SYMBOL
-0xbc11bbc3 iscsi_eh_abort drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x83e5c3a2 cx8802_fini_common drivers/media/video/cx88/cx8802
EXPORT_SYMBOL
0x9ef1615c request_key vmlinux EXPORT_SYMBOL
0x87c7272f __fscache_read_or_alloc_pages fs/fscache/fscache
EXPORT_SYMBOL
@@ -2574,7 +2597,6 @@
0x2b02b3f5 hpsb_get_tlabel drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xe63ba0b4 pci_do_scan_bus vmlinux EXPORT_SYMBOL
0x55097d3b bt_sock_unlink net/bluetooth/bluetooth EXPORT_SYMBOL
-0xf040633b iscsi_add_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x4a368ee3 ves1x93_attach drivers/media/dvb/frontends/ves1x93
EXPORT_SYMBOL
0x224f1c76 ide_register_hw_with_fixup vmlinux EXPORT_SYMBOL
0x1dcaa0c8 v4l2_prio_max drivers/media/video/v4l2-common
EXPORT_SYMBOL
@@ -2586,7 +2608,6 @@
0x52524a17 hpsb_iso_recv_unlisten_channel
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x2faa8ef9 usb_hcd_resume_root_hub vmlinux EXPORT_SYMBOL_GPL
0x98427c58 securityfs_remove vmlinux EXPORT_SYMBOL_GPL
-0x71b9b5e8 iscsi_check_assign_cmdsn drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xcc28624a hostap_set_string
drivers/net/wireless/hostap/hostap EXPORT_SYMBOL
0x437749bf videobuf_mmap_setup drivers/media/video/video-buf
EXPORT_SYMBOL_GPL
0x734e083f tpm_calc_ordinal_duration drivers/char/tpm/tpm
EXPORT_SYMBOL_GPL
@@ -2618,7 +2639,6 @@
0xfc7476fb dvb_pll_microtune_4042
drivers/media/dvb/frontends/dvb-pll EXPORT_SYMBOL
0x30bfe0e0 kmap_high vmlinux EXPORT_SYMBOL
0x79ad224b tasklet_kill vmlinux EXPORT_SYMBOL
-0xcefc5fbb iscsi_if_destroy_session_done
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x009072b2 scsi_print_command drivers/scsi/scsi_mod
EXPORT_SYMBOL
0xeb424b8f dvb_unregister_frontend
drivers/media/dvb/dvb-core/dvb-core EXPORT_SYMBOL
0xd4030763 __gameport_register_port
drivers/input/gameport/gameport EXPORT_SYMBOL
@@ -2631,7 +2651,6 @@
0x84be96bb sk_stop_timer vmlinux EXPORT_SYMBOL
0x94aac529 pcmcia_register_driver vmlinux EXPORT_SYMBOL
0x00d7f04d locks_remove_posix vmlinux EXPORT_SYMBOL
-0x08674e01 iscsi_unregister_transport
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x60769d88 pcie_port_service_unregister vmlinux EXPORT_SYMBOL
0x103aa537 radix_tree_delete vmlinux EXPORT_SYMBOL
0x9320ec72 dm_table_flush_all drivers/md/dm-mod
EXPORT_SYMBOL
@@ -2826,7 +2845,6 @@
0x1e6d26a8 strstr vmlinux EXPORT_SYMBOL
0x794487ee disable_hlt vmlinux EXPORT_SYMBOL
0xf890fe7f pm_idle vmlinux EXPORT_SYMBOL
-0xad53bc76 iscsi_prep_scsi_cmd_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x285dfffe mpt_proc_root_dir drivers/message/fusion/mptbase
EXPORT_SYMBOL
0x447ec1bc cx24110_pll_write
drivers/media/dvb/frontends/cx24110 EXPORT_SYMBOL
0x312e5334 k8_northbridges vmlinux EXPORT_SYMBOL
@@ -2868,7 +2886,6 @@
0xf8c5cdec d_alloc_anon vmlinux EXPORT_SYMBOL
0x6f2e907f copy_strings_kernel vmlinux EXPORT_SYMBOL
0x916bad0d __wait_on_bit vmlinux EXPORT_SYMBOL
-0xce7cf8ca iscsi_recv_pdu drivers/scsi/scsi_transport_iscsi
EXPORT_SYMBOL_GPL
0x04403fcf unregister_capi_driver drivers/isdn/capi/kernelcapi
EXPORT_SYMBOL
0x20645642 drm_debug drivers/char/drm/drm EXPORT_SYMBOL
0xac7d087b led_trigger_register_simple vmlinux
EXPORT_SYMBOL_GPL
@@ -2991,7 +3008,6 @@
0xaeea0069 acpi_run_oshp vmlinux EXPORT_SYMBOL_GPL
0x4f2cd6e8 snd_cs4231_info_double sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0x0e9e79d5 xdr_encode_opaque net/sunrpc/sunrpc
EXPORT_SYMBOL
-0xf640e867 iscsi_session_recovery_timedout drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xe6dbcd72 rtc_class_close drivers/rtc/rtc-core
EXPORT_SYMBOL_GPL
0x7b5d4b7a ib_is_mad_class_rmpp drivers/infiniband/core/ib_mad
EXPORT_SYMBOL
0x05949c77 snd_timer_global_unregister sound/core/snd-timer
EXPORT_SYMBOL
@@ -3097,7 +3113,6 @@
0x107d6ba3 __get_free_pages vmlinux EXPORT_SYMBOL
0xcb216f1e find_task_by_pid_type vmlinux EXPORT_SYMBOL
0xbb189cad disallow_signal vmlinux EXPORT_SYMBOL
-0xe71028ea iscsi_pool_init drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xdbcd416e sysctl_ip_nonlocal_bind vmlinux EXPORT_SYMBOL
0xeedd9ef6 pciserial_init_ports vmlinux EXPORT_SYMBOL_GPL
0x3b131d8d matroxfb_g450_shutdown
drivers/video/matrox/matroxfb_g450 EXPORT_SYMBOL
@@ -3133,7 +3148,6 @@
0x540f9040 acpi_os_sleep vmlinux EXPORT_SYMBOL
0x3d0dfdea vfs_rename vmlinux EXPORT_SYMBOL
0x5497aa2d generic_ro_fops vmlinux EXPORT_SYMBOL
-0x09adf54c iscsi_free_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xb819e673 hpsb_set_hostinfo drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xa29b16c9 kthread_bind vmlinux EXPORT_SYMBOL
0x833a3e07 snd_midi_channel_set_clear
sound/core/seq/snd-seq-midi-emul EXPORT_SYMBOL
@@ -3371,7 +3385,6 @@
0x56eea045 fb_blank vmlinux EXPORT_SYMBOL
0x4ddc4b9f utf8_mbtowc vmlinux EXPORT_SYMBOL
0x51a880ca open_exec vmlinux EXPORT_SYMBOL
-0x54efe73e iscsi_remove_session
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x53854e7d acpi_initialize_subsystem vmlinux EXPORT_SYMBOL
0xb80d62df mb_cache_entry_find_next vmlinux EXPORT_SYMBOL
0x656d7190 ip_vs_skb_replace net/ipv4/ipvs/ip_vs
EXPORT_SYMBOL
@@ -3393,7 +3406,6 @@
0xf4965aaf qdisc_lock_tree vmlinux EXPORT_SYMBOL
0x9ceca2f1 mempool_create_node vmlinux EXPORT_SYMBOL
0x4958824b scsi_bios_ptable drivers/scsi/scsi_mod
EXPORT_SYMBOL
-0xa1418b12 iscsi_verify_itt drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x3074f033 drm_order drivers/char/drm/drm EXPORT_SYMBOL
0xbfb37234 dev_set_promiscuity vmlinux EXPORT_SYMBOL
0xe7ecaf45 snd_mpu401_uart_interrupt
sound/drivers/mpu401/snd-mpu401-uart EXPORT_SYMBOL
@@ -3470,7 +3482,6 @@
0xf9448805 seq_path vmlinux EXPORT_SYMBOL
0xcc5005fe msleep_interruptible vmlinux EXPORT_SYMBOL
0xf8b2ff6e g_verify_token_header net/sunrpc/auth_gss/auth_rpcgss
EXPORT_SYMBOL
-0x02ae6629 iscsi_session_setup drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xf5767401 hpsb_update_config_rom drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0x65414e67 dev_valid_name vmlinux EXPORT_SYMBOL
0x3be89d3c usb_register_notify vmlinux EXPORT_SYMBOL_GPL
@@ -4030,7 +4041,6 @@
0xe61b6e89 generic_listxattr vmlinux EXPORT_SYMBOL
0x5bc201be kmem_cache_zalloc vmlinux EXPORT_SYMBOL
0xff2193fa ieee80211softmac_start
net/ieee80211/softmac/ieee80211softmac EXPORT_SYMBOL_GPL
-0xb31cb3ec iscsi_prep_unsolicit_data_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x67e33bda mptscsih_io_done drivers/message/fusion/mptscsih
EXPORT_SYMBOL
0xf1490f9a csr1212_release_keyval drivers/ieee1394/ieee1394
EXPORT_SYMBOL
0xf6ebc03b net_ratelimit vmlinux EXPORT_SYMBOL
@@ -4090,7 +4100,6 @@
0xfcec0987 enable_irq vmlinux EXPORT_SYMBOL
0x1e7bbcb3 kernel_restart vmlinux EXPORT_SYMBOL_GPL
0x9c7077bd enable_hlt vmlinux EXPORT_SYMBOL
-0x3c85f0a3 iscsi_set_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xce7e0ce2 sata_phy_resume drivers/scsi/libata
EXPORT_SYMBOL_GPL
0x8b9999be bt878_device_control drivers/media/dvb/bt8xx/bt878
EXPORT_SYMBOL
0x43837ebc b1_getrevision drivers/isdn/hardware/avm/b1
EXPORT_SYMBOL
@@ -4133,7 +4142,6 @@
0x50679ae0 FsmRestartTimer drivers/isdn/hisax/hisax
EXPORT_SYMBOL
0xc31f224a gameport_unregister_port
drivers/input/gameport/gameport EXPORT_SYMBOL
0xa0d95792 ip_route_input vmlinux EXPORT_SYMBOL
-0x738899f9 iscsi_conn_teardown drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x80e66d5a device_remove_file vmlinux EXPORT_SYMBOL_GPL
0xbf19c9c8 hpsb_allocate_and_register_addrspace
drivers/ieee1394/ieee1394 EXPORT_SYMBOL
0x29c14226 ipv6_skip_exthdr vmlinux EXPORT_SYMBOL
@@ -4683,7 +4691,6 @@
0x9cbe4d8f ib_create_cm_id drivers/infiniband/core/ib_cm
EXPORT_SYMBOL
0xf338d4c3 netlink_unregister_notifier vmlinux EXPORT_SYMBOL
0x04104e78 simple_release_fs vmlinux EXPORT_SYMBOL
-0x7452449d iscsi_change_queue_depth drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xb189a6d9 ipmi_create_user
drivers/char/ipmi/ipmi_msghandler EXPORT_SYMBOL
0x500145db generic_file_aio_write_nolock vmlinux EXPORT_SYMBOL
0xcef7cefe scsi_host_put drivers/scsi/scsi_mod EXPORT_SYMBOL
@@ -4872,7 +4879,6 @@
0x243d71d6 generic_write_checks vmlinux EXPORT_SYMBOL
0xd6035d05 do_settimeofday vmlinux EXPORT_SYMBOL
0x72270e35 do_gettimeofday vmlinux EXPORT_SYMBOL
-0x7d88a1fb iscsi_session_get_param drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x68ef30a6 uart_match_port vmlinux EXPORT_SYMBOL
0x36d5355b acpi_register_gsi vmlinux EXPORT_SYMBOL
0xf8962595 destroy_8023_client net/802/p8023 EXPORT_SYMBOL
@@ -5077,7 +5083,6 @@
0xc55f528f usb_sg_cancel vmlinux EXPORT_SYMBOL
0x25740865 struct_module vmlinux EXPORT_SYMBOL
0x0f2103ff snd_emux_new sound/synth/emux/snd-emux-synth
EXPORT_SYMBOL
-0xfd9f41f8 iscsi_destroy_conn
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x9f07a59b ib_register_device drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0x6d41d8df nf_register_queue_handler vmlinux EXPORT_SYMBOL
0x5fb31e7e pcmcia_get_status vmlinux EXPORT_SYMBOL
@@ -5135,7 +5140,6 @@
0xd381cfa5 usb_driver_claim_interface vmlinux EXPORT_SYMBOL
0x01139ffc max_mapnr vmlinux EXPORT_SYMBOL
0xb24aa0ed snd_opl3_reset sound/drivers/opl3/snd-opl3-lib
EXPORT_SYMBOL
-0x9ede8aa5 iscsi_conn_failure drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x865e1b56 dvb_pll_lg_z201 drivers/media/dvb/frontends/dvb-pll
EXPORT_SYMBOL
0x368518de led_trigger_set vmlinux EXPORT_SYMBOL_GPL
0x07e93cdc snd_pcm_mmap_data sound/core/snd-pcm
EXPORT_SYMBOL
@@ -5266,7 +5270,6 @@
0xe535efb8 cdrom_mode_sense drivers/cdrom/cdrom
EXPORT_SYMBOL
0xf4f52f93 dqstats vmlinux EXPORT_SYMBOL
0x9a6ea734 mb_cache_entry_release vmlinux EXPORT_SYMBOL
-0x3340bfd1 iscsi_conn_send_pdu drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0xd45b5eb5 capi_cmsg2str drivers/isdn/capi/kernelcapi
EXPORT_SYMBOL
0xa6bda823 ib_query_qp drivers/infiniband/core/ib_core
EXPORT_SYMBOL
0x8df296f8 snd_ak4531_suspend sound/pci/ac97/snd-ak4531-codec
EXPORT_SYMBOL
@@ -5446,7 +5449,6 @@
0x1eb922a3 IO_APIC_get_PCI_irq_vector vmlinux EXPORT_SYMBOL
0x30f23b16 snd_cs4236_ext_out sound/isa/cs423x/snd-cs4231-lib
EXPORT_SYMBOL
0xb70fbe06 nfs4_acl_free fs/nfsd/nfsd EXPORT_SYMBOL
-0xf53fce1c iscsi_register_transport
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0x1a12dda7 netlink_ack vmlinux EXPORT_SYMBOL
0x397b8738 sock_no_bind vmlinux EXPORT_SYMBOL
0x8335ce68 sock_get_timestamp vmlinux EXPORT_SYMBOL
@@ -5503,7 +5505,6 @@
0xd60ded4d bus_unregister vmlinux EXPORT_SYMBOL_GPL
0x69b7b928 __elv_add_request vmlinux EXPORT_SYMBOL
0x604a58fd set_bh_page vmlinux EXPORT_SYMBOL
-0x7fb2d2c4 iscsi_if_create_session_done
drivers/scsi/scsi_transport_iscsi EXPORT_SYMBOL_GPL
0xd38d8ae2 hermes_read_ltv drivers/net/wireless/hermes
EXPORT_SYMBOL
0x28402f7c cx8802_resume_common drivers/media/video/cx88/cx8802
EXPORT_SYMBOL
0xa0e26709 parport_ieee1284_read_byte drivers/parport/parport
EXPORT_SYMBOL
@@ -5617,7 +5618,6 @@
0x4d6908b2 _atomic_dec_and_lock vmlinux EXPORT_SYMBOL
0xea7987f1 key_update vmlinux EXPORT_SYMBOL
0xe8b4c87c simple_prepare_write vmlinux EXPORT_SYMBOL
-0x71a7d5f6 iscsi_conn_bind drivers/scsi/libiscsi
EXPORT_SYMBOL_GPL
0x129ec2d2 xfrm_register_km vmlinux EXPORT_SYMBOL
0x57b8433a ip_mc_dec_group vmlinux EXPORT_SYMBOL
0xcb7131fb fb_get_options vmlinux EXPORT_SYMBOL
But alas, it still doesn't work. Here's the output of dmesg:
Carlos Rimola
to keep up with everything, but I am a strong believer in Open Source
and iSCSI as the new and rapidly growing foundation for Storage Area
Networks, and I would like to contribute to the efforts of Open-iSCSI
because I would hate to see Linux be left behind in this key area of
market adaptation.
My background - I worked with Alex and Dimitry (Dima) [and a genius
Frenchman ;-)] on one of the first robust implementations of an iSCSI
Initiator and Target that can run both in embedded (firmware) as well as
a Linux loadable module. We worked together for about 3 years at
Silverback Systems (best TOE + iSCSI Offload Engine [IOE]) in the
market. My role was mainly working on the iSCSI Control Plane but I
understand the Data Plane (Critical Path) well enough.
Ok, my main question is how do I become an official contributor? I
could have asked Alex or Dimitry directly but I want to go through the
process as I have not participated in an Open Source project before.
One area that I see seriously lacking in Linux iSCSI SAN support is
centralized and easy to use management and provisioning. It seems like
all the vendors are coming up with their own proprietary solutions and
this takes us down the path of FC (it regresses the benefits of iSCSI).
Please correct me if I am wrong. It seems like SNIA is making a good
attempt to standardize Management APIs [SMI-S Framework which include
the key iSCSI Management API (IMA) and the MultiPath Management API
(MMA)]. The question is will the Target and Initiator vendors fall
behind and expose these APIs? SNIA claims there is already strong
support on the part of the big players.
I do have some important questions about Open-iSCSI:
1) Does it support Discovery via iSNS
2) If the answer to #1 is yes, is the iSNS client integrated w/ the
Initiator or is it a separate (user space?) component.
3) This is more of a comment, if Open-iSCSI does not support iSNS, it
will limit its ability to enter the Enterprise Market.
4) Does Open-iSCSI support Zoning and LUN Masking? Centralized
Management?
5) What about Authentication management, including Radius support and
management of Initiator Name (or identifier) to CHAP secrets?
Maybe what I am mainly asking is - where is the Open-iSCSI FAQ and do we
recognize how important the above issues are?
Thanks and Best Regards to All members,
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
Next Generation Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
Mike Christie
> Ok, my main question is how do I become an official contributor? I
Figure out something to do and send patches or write new code. That's it. :)
> Symantec Corporation
Forget management and feature XYZ. Go talk to whoever is doing iscsi at
Symantec and help them replicate their out of memory problem with
open-iscsi and a mainline kernel so we can make sure this problem gets
fixed. Email me offline and I will give you some red hat - symantec
bugzillas for this which require you guys to just try out open-iscsi
with a mainline kernel so we can pin point the problem and try to fix
it. Before you worry about ease of management, you should:
- try open-iscsi to see some of your questions are answered
- do a search of the archives to see some of your questions are answered
- make sure we can reliably write data
I do not mean this in a mean way. A common first step to working on a
project is to get comfortable with the code and tools so you know what
sucks and what needs fixing/implementing. A lot of what you wrote are
good ideas and should be done and a lot have been discussed over and
over again and we really need to get the OOM problem resolved and for
some reason your company is the only one that is hitting it in a recent
2.6 kernel but we need them to try it out with open-iscsi.
Carlos Rimola
No excuses here but I did state that lack of time may limit my
contribution(s). As much as I appreciate the technology and I am
willing to throw some of my limited spare time into it. However, my
family and quality time with them comes first.
I like your sense of candidness, just be aware that I can be equally
candid. Your first answer was very useful but you could have helped me
more and the open-iscsi effort by answering my key questions.
Even though we never met, I know you have been a key contributor to this
effort and I respect your contributions so don't take this as
belligerence.
Ok, answers/opinions interjected:
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Mike Christie
> Sent: Wednesday, November 01, 2006 11:02 PM
> To: open-...@googlegroups.com
> Subject: Re: Hello Open-iSCSI World
>
>
> Carlos Rimola wrote:
> > Ok, my main question is how do I become an official contributor? I
>
> Figure out something to do and send patches or write new code. That's
it.
> :)
Good enough, though it would be good to know and agree on what is
lacking in open-iscsi at the moment and focus on that. Also, a hint
about procedures like CVS repository would be useful. I can ask Dima or
Alex directly but I figured this is information that will benefit other
"would be" contributors.
>
> > Symantec Corporation
>
> Forget management and feature XYZ. Go talk to whoever is doing iscsi
at
> Symantec and help them replicate their out of memory problem with
> open-iscsi and a mainline kernel so we can make sure this problem gets
> fixed. Email me offline and I will give you some red hat - symantec
> bugzillas for this which require you guys to just try out open-iscsi
> with a mainline kernel so we can pin point the problem and try to fix
> it.
Ok, it sounds like you have a beef with Symantec about a problem or
problems that have not been addressed. I can definitely help but this
falls outside the realm of me wanting to contribute to open-iscsi.
Let's take this offline and send me your gripes, I will make sure they
get addressed.
> Before you worry about ease of management, you should:
>
> - try open-iscsi to see some of your questions are answered
> - do a search of the archives to see some of your questions are
answered
> - make sure we can reliably write data
I don't get the last one but the first two are commonly known. However,
if someone is willing to contribute to the effort, it is common courtesy
to get them up to speed by answering their initial set of questions?
>
> I do not mean this in a mean way. A common first step to working on a
> project is to get comfortable with the code and tools so you know what
> sucks and what needs fixing/implementing. A lot of what you wrote are
> good ideas and should be done and a lot have been discussed over and
> over again and we really need to get the OOM problem resolved and for
> some reason your company is the only one that is hitting it in a
recent
> 2.6 kernel but we need them to try it out with open-iscsi.
Fair enough but I do want to keep company and person (me) separate from
this. Perhaps, I should have disabled the automatic signature
insertion. Nevertheless, I will be glad to help resolve any issues
involving "the company" and open-iscsi.
I understand your "common first step(s)" but I preceded my message by
stating that I have not participated in an Open-Source project before.
I can and will work my way through what you suggest but some quick
pointers would have been a lot more meaningful.
Anyway, peace and the only favor I ask is that we keep person and
company one works for as separate entities. My aim is to help the
development of open-iscsi. This has nothing to do with who I work for
and in what capacity.
Carlos
Christoph Hellwig
> Ok, my main question is how do I become an official contributor?
You don't. There's no official contributor status. You will become a
major contributor by making lots of usefull contributions and asking less
stupid questions and stop preading marketing bullshit.
Christoph Hellwig
> One area that I see seriously lacking in Linux iSCSI SAN support is
> centralized and easy to use management and provisioning. It seems like
> all the vendors are coming up with their own proprietary solutions and
> this takes us down the path of FC (it regresses the benefits of iSCSI).
> Please correct me if I am wrong. It seems like SNIA is making a good
> attempt to standardize Management APIs [SMI-S Framework which include
> the key iSCSI Management API (IMA) and the MultiPath Management API
> (MMA)]. The question is will the Target and Initiator vendors fall
> behind and expose these APIs? SNIA claims there is already strong
> support on the part of the big players.
No, we are not going to put in the junk SNIA designed. Having useful
managment APIs (and with that I mean actually useful, not standardized
by a comitee of crack smokers) is very welcome. The Implementation
should be in the iscsi transport class at the kernel level, talking
to a shared library with useful command line tools as reference
implementation. If you plan to do a GUI on top of that that would be
even more nice, but secondary to the basic implementation.
> I do have some important questions about Open-iSCSI:
>
> 1) Does it support Discovery via iSNS
>
> 2) If the answer to #1 is yes, is the iSNS client integrated w/ the
> Initiator or is it a separate (user space?) component.
>
> 3) This is more of a comment, if Open-iSCSI does not support iSNS, it
> will limit its ability to enter the Enterprise Market.
>
> 4) Does Open-iSCSI support Zoning and LUN Masking? Centralized
> Management?
>
> 5) What about Authentication management, including Radius support and
> management of Initiator Name (or identifier) to CHAP secrets?
Please take a look at the code. Open-iSCSI is a very small and lean
codebase, and you need to become familar with it anyway to be able to
contribute to it.
Also looking at the recent mailinglist archives might easily answer
questions not answered by the code - if you still have any left
afterwards feel free to restate them.
Mike Christie
> Mike,
>
> No excuses here but I did state that lack of time may limit my
> contribution(s). As much as I appreciate the technology and I am
> willing to throw some of my limited spare time into it. However, my
> family and quality time with them comes first.
Hey, perfectly fair :)
>
> I like your sense of candidness, just be aware that I can be equally
> candid. Your first answer was very useful but you could have helped me
> more and the open-iscsi effort by answering my key questions.
>
> Even though we never met, I know you have been a key contributor to this
> effort and I respect your contributions so don't take this as
> belligerence.
>
> Ok, answers/opinions interjected:
>
>> -----Original Message-----
>> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
> On
>> Behalf Of Mike Christie
>> Sent: Wednesday, November 01, 2006 11:02 PM
>> To: open-...@googlegroups.com
>> Subject: Re: Hello Open-iSCSI World
>>
>>
>> Carlos Rimola wrote:
>>> Ok, my main question is how do I become an official contributor? I
>> Figure out something to do and send patches or write new code. That's
> it.
>> :)
>
> Good enough, though it would be good to know and agree on what is
What really is lacking in open-iscsi right now is what I mentioned in
the previous mail. We need to be able to tell usrs that the OOM problem
does not exist in 2.6 or replicate it and solve it.
> lacking in open-iscsi at the moment and focus on that. Also, a hint
If you are going to work on this for fun, you should pick out what you
think is lacking in the project and what you think is interesting. You
really do not need to go by our priority list since we do not have one
and if we had a formal one the top of the list would be very boring. It
would be bugfixes and cleanups.
As far as managemnt goes:
Everyone on the list will probably not agree on what the most important
management feature is. Users might say iSNS. Most will probably say the
basics still need to be done and fixed and working init scripts would be
nice. The latter would help out a lot of people but is not exiting like
adding iSNS.
If you want to work on management features like what you mentioned you
should just check out the code and take a minute to do some basic
research. Below is some comments but the discussion about these items,
except radius, has sometimes been very very long and this short summary
will not be enough.
- If you look through the list you will see we have lots of interest in
iSNS. Tomo has been doing work on it. He is also trying to integrate HW
iscsi support in now. It would be best to search the list for past
discussions and work with him on this since he probably has a good plan
on how he can share his code between the initiator and target and
support hw iscsi.
- Radius support would be nice.
- Any type of management improvements would be nice. Watch out for the
SNIA land mines. If you are going to add support for something like that
have a good defense about why you think it is a good idea. Search the
list for the people that do not like SNIA specs and talk to them to see why.
- If you look through the list, you will see we are at the very basic
stages of being able to manage the initiator. Right now we just want to
do things like be able to manage SW iscsi and HW iscsi from the same
tools. If you check upstream, you will see qla4xxx just got merged and
if you look through the list you will see that we have only very basic
support for it. If modifying the existing tools so that they manage all
types of iscsi initiators sounds interesting, I would email DaveS at
Qlogic to see where he needs help.
> about procedures like CVS repository would be useful. I can ask Dima or
> Alex directly but I figured this is information that will benefit other
> "would be" contributors.
Hey, sorry. I thought the send patches comment was enough. I did not
know you were asking what to make patches against or maybe how to make
patches.
For kernel code you should download the iscsi git tree here:
http://kernel.org/git/?p=linux/kernel/git/mnc/linux-2.6-iscsi.git;a=summary
checkout out the iscsi branch
For userspace code send patches against the svn code.
See git docs on how to make a patch with git. See the kernel
documentation about how to make a patch and send it to a list (any linux
kernel related list).
http://lxr.linux.no/source/Documentation/SubmittingPatches
Basically, diff the source with -aup and if you embed the mail use a
mailer that does not wrap the patch. We also accept patches attached if
other mailers can easily reply to the mail and the patch is magically
embedded in the reply. Other mailing lists may always want the patch
inlined. When you send the patch include a signed off for kernel stuff
and don't forget to add a decent description of the patch that can be
forwarded upstream and will be the the patch summary.
>
>>> Symantec Corporation
>> Forget management and feature XYZ. Go talk to whoever is doing iscsi
> at
>> Symantec and help them replicate their out of memory problem with
>> open-iscsi and a mainline kernel so we can make sure this problem gets
>> fixed. Email me offline and I will give you some red hat - symantec
>> bugzillas for this which require you guys to just try out open-iscsi
>> with a mainline kernel so we can pin point the problem and try to fix
>> it.
>
> Ok, it sounds like you have a beef with Symantec about a problem or
Just to be clear there is no problem with them. I did not mean it like
that. At this point running normal IO is risky because of the feared out
of memory problem. Symantec has a setup where they can hit the problem
by just running dd. No one else has been able to hit it and we cannot
replicate the problem here. It is a pretty important bug. Until that is
confirmed in current kernels with open-iscsi and solved then all the
managment features you can add are not worth much since it would seem
strange to tell people that we have the best management tools in the
world but oh yeah you may or may not want to store data on the iscsi
disks because the can sometimes die because we messed up when we
allocate memory for them :)
Apparently the Symantec iscsi guy moved on. We have been waiting for a
new symantec iscsi developer to take his place and for symantec to
replicate the problem with open-iscsi. Since you work there I hoped you
could help. I will ping you offline.
> problems that have not been addressed. I can definitely help but this
> falls outside the realm of me wanting to contribute to open-iscsi.
> Let's take this offline and send me your gripes, I will make sure they
> get addressed.
>
>> Before you worry about ease of management, you should:
>>
>> - try open-iscsi to see some of your questions are answered
>> - do a search of the archives to see some of your questions are
> answered
>> - make sure we can reliably write data
>
> I don't get the last one but the first two are commonly known. However,
> if someone is willing to contribute to the effort, it is common courtesy
> to get them up to speed by answering their initial set of questions?
I had always thought it was common courtesy for the new guy to do some
basic research before posting. At least look at the code for a little
bit and see that most of the questions are already answered in there, so
we are not wasting people's time rehashing things. You will have to look
at the source one day so you might as well do it right away. So maybe we
both think we are being rude to each other I guess :)
I do apologize for the rudeness to you.
>
>> I do not mean this in a mean way. A common first step to working on a
>> project is to get comfortable with the code and tools so you know what
>> sucks and what needs fixing/implementing. A lot of what you wrote are
>> good ideas and should be done and a lot have been discussed over and
>> over again and we really need to get the OOM problem resolved and for
>> some reason your company is the only one that is hitting it in a
> recent
>> 2.6 kernel but we need them to try it out with open-iscsi.
>
> Fair enough but I do want to keep company and person (me) separate from
Yeah, no problem.
Mike Christie
>
>> about procedures like CVS repository would be useful. I can ask Dima or
>> Alex directly but I figured this is information that will benefit other
>> "would be" contributors
It seems that some would be contributors prefer to ask the list for what
is in the list archives so I am not sure how useful my last response
will be. If someone posts a again about this I will have to search the
archives and point it out to them. And all of this reminds me of another
major lacking item: good documentation.
- The wiki is out of date. Spammers took it over for a while and
voltaire tried to battle them.
- A lot of the iscsi settings are not documented. We could use a
iscsid.conf man page describing all the values.
- We probably need a super newbies guide to iscsi and how to run open-iscsi.
- We need a guide for how to setup iscsi with dm. What settings are
optimal, how to setup dm multipath with open-iscsi, etc.
- We should document what targets we work with and what limitations we
found. The wiki is out of date. Users are searching the list to find
this info instead of using the old wiki.
Mark Blondin
I have been lurking for a while trying to learn something. This seems to be an active community and I have learned a bit. If anyone is in the market for an iSCSI system from the leading manufacturer, please let me know.
Mark
Carlos Rimola
This is a rather obnoxious response and a show of character that will
not help advance the open-iscsi cause which I hope is our common
interest here.
I have been around the circuit ;-) and if this is how you choose to
communicate I will probably simply ignore you. I have no time for
infantile upmanship, no matter what your level of knowledge is on the
subject at hand.
Carlos
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
Next Generation Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Christoph Hellwig
> Sent: Thursday, November 02, 2006 3:17 AM
> To: open-...@googlegroups.com
> Subject: Re: Hello Open-iSCSI World
>
>
Carlos Rimola
hope).
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Christoph Hellwig
> Sent: Thursday, November 02, 2006 3:21 AM
> To: open-...@googlegroups.com
> Subject: Re: Hello Open-iSCSI World
>
>
> And now off from principal things to the technical bits in here:
>
> > One area that I see seriously lacking in Linux iSCSI SAN support is
> > centralized and easy to use management and provisioning. It seems
like
> > all the vendors are coming up with their own proprietary solutions
and
> > this takes us down the path of FC (it regresses the benefits of
iSCSI).
> > Please correct me if I am wrong. It seems like SNIA is making a
good
> > attempt to standardize Management APIs [SMI-S Framework which
include
> > the key iSCSI Management API (IMA) and the MultiPath Management API
> > (MMA)]. The question is will the Target and Initiator vendors fall
> > behind and expose these APIs? SNIA claims there is already strong
> > support on the part of the big players.
>
> No, we are not going to put in the junk SNIA designed. Having useful
> managment APIs (and with that I mean actually useful, not standardized
> by a comitee of crack smokers) is very welcome. The Implementation
> should be in the iscsi transport class at the kernel level, talking
> to a shared library with useful command line tools as reference
> implementation. If you plan to do a GUI on top of that that would be
> even more nice, but secondary to the basic implementation.
>
Well, I am Crack Smoker but not an SNIA Contributor so go figure.. ;-)
That is completely a joke btw. The last thing I need is someone
knocking on my door to search for drugs!
I beg to differ with you on this. I believe that one of the keys to
iSCSI based SANs potential success (and why is rapidly taking off) is
the adoption of open and interoperable standards across platforms. We
all love Linux and Linux based Solutions but in the iSCSI market you
have to interoperate with other platforms (mainly MS right now) or we
will be displaced. Current iSCSI SAN deployment is about 80% MS based
and less than 20% Linux based. Let's analyze the reasons and work to
change that..
> > I do have some important questions about Open-iSCSI:
> >
> > 1) Does it support Discovery via iSNS
> >
> > 2) If the answer to #1 is yes, is the iSNS client integrated w/ the
> > Initiator or is it a separate (user space?) component.
> >
> > 3) This is more of a comment, if Open-iSCSI does not support iSNS,
it
> > will limit its ability to enter the Enterprise Market.
> >
> > 4) Does Open-iSCSI support Zoning and LUN Masking? Centralized
> > Management?
> >
> > 5) What about Authentication management, including Radius support
and
> > management of Initiator Name (or identifier) to CHAP secrets?
>
> Please take a look at the code. Open-iSCSI is a very small and lean
> codebase, and you need to become familar with it anyway to be able to
> contribute to it.
I am doing so as we speak. Thanks for the tip.. Mike Christie
suggested this as well.
>
> Also looking at the recent mailinglist archives might easily answer
> questions not answered by the code - if you still have any left
> afterwards feel free to restate them.
>
This is another good tip which Mike also has referred me to pursue.
Carlos
>
Carlos Rimola
All I can say is - very useful feedback here in all aspects. I wish I
had more time to elaborate but this will be very helpful to advance the
cause..
Carlos
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
SANVM Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
Carlos Rimola
Thanks!
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
SANVM Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Mike Christie
> Sent: Thursday, November 02, 2006 8:36 AM
> To: open-...@googlegroups.com
> Subject: Re: Hello Open-iSCSI World
>
>
Carlos Rimola
I am not sure what this has to do with my post. I imagine you work for
NetApp. This is better handled offline or it may be construed as simple
marketing gibberish. No offense meant..
Carlos
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
Next Generation Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
Christoph Hellwig
>
> Ok,
>
> not help advance the open-iscsi cause which I hope is our common
> interest here.
>
> I have been around the circuit ;-) and if this is how you choose to
> communicate I will probably simply ignore you. I have no time for
> infantile upmanship, no matter what your level of knowledge is on the
> subject at hand.
Well, your question has been utterly stupid so you'll get a stupid
answer. And while you're at it please get a RFC-compliant mailer
and stop top-posting if you want to participate on Linux mailinglists.
Carlos Rimola
communication, we are done and your messages will go directly into the
bit bucket. I won't even see them..
Unfortunately, as Symantec is a rather large company I am forced to use
Outlook (never used it before coming here).
"Stupid questions and answers" are a totally subjective definition. A
Stupid attitude is much less so. Lighten up!
Carlos
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
Next Generation Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Christoph Hellwig
> Sent: Thursday, November 02, 2006 2:20 PM
> To: open-...@googlegroups.com
> Subject: Re: Hello Open-iSCSI World
>
>
Albert Pauw
between me and Erez trying to fix a problem after which it was
highjacked
and the subject changed. Speaking about nettiquette.
I have worked with Mike and many others on this list trying to solve
problems (where I only contribute as a tester) and if Carlos had read
through
the archives he would have noticed that open-iscsi has come a long way
and stability has improved dramatically. Since it is a community
project
and not a highly paid project I would say it does quite well so far,
thanks to everyone. Bullying yourself into it doesn't give yourself
high
status, contributions do.
Just my two cents,
Albert
P.S. Let's consider this thread closed please (sigh).
Carlos Rimola
should have done some more research prior to my first post and set of
questions. I don't want to stir up things in a project that is making a
valuable contribution to Linux in the IP/iSCSI SAN space.
I shall keep a low profile and find the answers by looking at the code
which I have already downloaded and I am now looking at.
You are right that contributions are what really count and that is my
motivation. Meanwhile, I shall stay out of the way of creating
unnecessary "noise".
Thanks for the feedback and as you suggest - thread closed (on my part).
I may revisit it but only if I find serious holes.
Carlos
Carlos Rimola
Symantec Corporation
Sr. Principal Software Engineer
Next Generation Storage Group
Tel.: 650-527-4505
Cell: 408-858-5548
> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com]
On
> Behalf Of Albert Pauw
> Sent: Thursday, November 02, 2006 11:11 PM
> To: open-iscsi
> Subject: Re: Hello Open-iSCSI World
>
>
Ming Zhang
noise.
There is no public TODO list for this project, document is outdated.
Similar many other OSS projects. A new comer will feel hard to jump in.
Especially for people that can only contribute several hours per week.
Mike has an internal TODO list I guess. There are some
things/tasks/wishes here and there in email list archive as well. But
since I joined this group in 02/24/2005, there are 6810 emails in this
open-iscsi folder. Finish reading them is not an easy task at all. So
why can not make things to be straight forward?
Of course, download the code, run it and feel it is the prerequisite to
join here. But a open attitude and warm welcome from project admin
should be nice as well. Shall we all read at least this chapter?
http://producingoss.com/html-chunk/managing-volunteers.html
Email is one of the easy way to offense people, so all of us should be
careful on this. Or unless you do not care about people at all.
Ming
Ming Zhang
<snip: long quarrel... ;)>
I just did a top post, reply it too quickly. sorry about that. for
people has question about this top post, pls read
http://www.xs4all.nl/~hanb/documents/quotingguide.html
and http://www.faqs.org/rfcs/rfc1855.html
but unfortunately, i know many people, especially those in big
companies, _like_ top post. and if we embedded the reply into original
text, they do not read it at all.
wish we can "welcome the same behavior and tolerate the different ones."
not the "you are our enemy if you are not our friends..."
Ming
Carlos Rimola
Just for the record, this refers to Albert's post - I did not hijack any thread. To be honest I am not even aware of what thread you refer to. Also, I am not trying to "bully" my way in.
I may be guilty of being a little naïve by offering my services and asking some questions that I could and should have found the answers to by reading the code and the archives. However, it is neither my nature nor my intent to offend anyone. If anyone felt offended, my apologies..
And with this, I hope we can declare the thread closed. Maybe my experience will help other "would be volunteers" not to make the same mistake.
Mike Christie
> I know this thread is ending, but still try to jump into and make some
> noise.
>
> There is no public TODO list for this project, document is outdated.
Do you mean the docs on the open-iscsi website or the docs in the
open-iscsi tarball/svn. Except to some references about still supporting
MC/S I think the docs are pretty much up to date. They are not complete
though.
There is lots of detail missing. As you see from emails, I am not the
best at writing so I have tried to not touch the docs much. Maybe in
this case something is better than nothing.
We will get the docs on the website updated when I get access to it.
> Similar many other OSS projects. A new comer will feel hard to jump in.
> Especially for people that can only contribute several hours per week.
>
> Mike has an internal TODO list I guess. There are some
I am actually still working off the todo list I posted back in March.
http://groups-beta.google.com/group/open-iscsi/msg/39df1882ca75bfbd?dmode=source
It should probably go into a wiki, but we need to do something about
that so we do not have to clean up from spammers every day.
Ming Zhang
> Ming Zhang wrote:
> > I know this thread is ending, but still try to jump into and make some
> > noise.
> >
> > There is no public TODO list for this project, document is outdated.
>
> Do you mean the docs on the open-iscsi website or the docs in the
> open-iscsi tarball/svn. Except to some references about still supporting
> MC/S I think the docs are pretty much up to date. They are not complete
> though.
i meant website. sorry that i did not read the README in svn for a
while. but the 2005 here is quite misleading. ;)
=================================================================
Linux* Open-iSCSI
=================================================================
January 20, 2005
>
> There is lots of detail missing. As you see from emails, I am not the
> best at writing so I have tried to not touch the docs much. Maybe in
> this case something is better than nothing.
>
> We will get the docs on the website updated when I get access to it.
>
> > Similar many other OSS projects. A new comer will feel hard to jump in.
> > Especially for people that can only contribute several hours per week.
> >
> > Mike has an internal TODO list I guess. There are some
>
> I am actually still working off the todo list I posted back in March.
> http://groups-beta.google.com/group/open-iscsi/msg/39df1882ca75bfbd?dmode=source
>
> It should probably go into a wiki, but we need to do something about
> that so we do not have to clean up from spammers every day.
yes, wiki is better. since open-iscsi is so actively developed, it is
hard to fully trust a todo list posted in March.
>
> >
Erez Zilber
Albert,
I think that I understand the problem (I had the same thing today):
after you build open-iscsi, you need to fix the version of its symbols.
This is already taken care of (using the script). Now, iSER should be
rebuilt with the new symbols. It worked for me. Let me know if this
solves your problem.
--
____________________________________________________________
Erez Zilber | 972-9-971-7689
Software Engineer, Storage Team
Voltaire – _The Grid Backbone_
__
Albert Pauw
> rebuilt with the new symbols. It worked for me. Let me know if this
> solves your problem.
Do you mean I have to recompile the kernel modules (in this case at
least iser) each time I update the open-iscsi source?
Erez Zilber
need to update Module.symvers and rebuild modules that use these
symbols. If you build the kernel module in the kernel tree, you don't
have this problem.
We don't have this problem because we compile iSER & open-iscsi from the
kernel tree (we use open-iscsi git tree). We use open-iscsi from svn
only for userspace code.
Erez