[rds-devel] testing with RDS on the mainline kernel

Or Gerlitz ogerlitz at voltaire.com
Wed May 14 07:26:29 PDT 2008


On Wed, 14 May 2008, Or Gerlitz wrote:
> in sync with your tree?!). The following two patches fix the compilation errors
> but I am remained with call to move_addr_to_kernel() which is not exported. How
> does it work on older kernels? is this function being exported there? any idea
> how to avoid this problem?

OK, I commented out the call to move_addr_to_kernel() and tried to load
the module, but it fails with:

[linux-2.6.26-rc2]# insmod net/rds/rds.ko
insmod: error inserting 'net/rds/rds.ko': -1 Cannot allocate memory

and the below errors at the dmesg, which seems harder to bypass just with
commenting out things (eventhough that I will try it!) can you help in
that, providing direction, etc.

thanks,

Or.

sysctl table check failed: /net/rds .3.9912 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/reconnect_min_delay_ms .3.9912.4 Missing strategy
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244a56>] sysctl_check_table+0x48b/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/reconnect_min_delay_ms .3.9912.4 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/reconnect_max_delay_ms .3.9912.5 Missing strategy
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244a56>] sysctl_check_table+0x48b/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/reconnect_max_delay_ms .3.9912.5 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/pf_rds .3.9912.6 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/sol_rds .3.9912.7 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/max_unacked_packets .3.9912.8 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/max_unacked_bytes .3.9912.9 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80

sysctl table check failed: /net/rds/ping_enable .3.9912.10 Unknown sysctl binary path
Pid: 8653, comm: insmod Not tainted 2.6.26-rc2 #1

Call Trace:
 [<ffffffff802445c3>] set_fail+0x3f/0x47
 [<ffffffff80244ac2>] sysctl_check_table+0x4f7/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80244add>] sysctl_check_table+0x512/0x535
 [<ffffffff80234866>] __register_sysctl_paths+0xd8/0x131
 [<ffffffffa021415e>] :rds:rds_sysctl_init+0x25/0x37
 [<ffffffffa021402f>] :rds:rds_init+0x2f/0xc0
 [<ffffffff8024d5b0>] sys_init_module+0x9d/0x1a7
 [<ffffffff8020b13b>] system_call_after_swapgs+0x7b/0x80





More information about the rds-devel mailing list