nfs41: sunrpc: handle clnt==NULL in call_status
Subsystems (3)
On the following error path task->tk_client == NULL causing NULL deref:
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000078 Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P) panlayoutdriver nfslayoutdriver nfsd auth_rpcgss exportfs nfs lockd nfs_acl fuse sunrpc ipv6 cpufreq_ondemand powernow_k8 freq_table dm_mirror dm_log dm_multipath dm_mod snd_hda_intel snd_seq_dummy sr_mod snd_seq_oss cdrom snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep snd pcspkr serio_raw k8temp hwmon forcedeth soundcore pata_amd sg jedec_probe cfi_probe gen_probe mtd i2c_nforce2 chipreg i2c_core button map_funcs sata_nv ata_generic pata_acpi libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan] Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P 2.6.27-pnfs #1 Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>] [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS: 00010246 Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX: 00000000ffffff95 RCX: 0000000000000000 Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI: ffff88002fc52dc0 RDI: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08: ffff88002f9dae40 R09: ffffffff81489e60 Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11: ffff88002a70bd30 R12: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14: ffff88002f57fa00 R15: ffff88002fc52e50 Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000) GS:ffffffff8148da80(0000) knlGS:0000000000000000 Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3: 000000002f971000 CR4: 00000000000006e0 Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405, threadinfo ffff88002a70a000, task ffff88003694d900) Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000 ffff88002f57fa00 ffff88002fc52dc0 ffff880030450ce8 Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db ffff88002a70bdf0 ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00 ffff880030450ce8 ffff88002a734000 Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>] __rpc_execute+0x7e/0x21f [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>] rpc_execute+0x28/0x2c [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>] rpc_run_bc_task+0x88/0xae [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>] bc_svc_process+0xf6/0x101 [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ? prepare_to_wait+0x5c/0x65 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>] nfs41_callback_svc+0xda/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ? autoremove_wake_function+0x0/0x38 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ? nfs41_callback_svc+0x0/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11 Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ? pick_next_task_fair+0x93/0xa3 Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ? child_rip+0x0/0x11 Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49 c7 44 24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30 e8 b9 2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00 f0 80 a2 Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---
---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)
net/sunrpc/clnt.c +5 -3
@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :
@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty)printk ("%s: RPC call returned error %d\n" , - clnt->cl_protname, -status); + clnt ? clnt->cl_protname :"<unknown protocol>" , + -status);rpc_exit (task, status); } }
Quoted 76 lines · Benny Halevy
On the following error path
task->tk_client== NULL causing NULL deref:Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000078 Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P) panlayoutdriver nfslayoutdriver nfsd auth_rpcgss exportfs nfs lockd nfs_acl fuse sunrpc ipv6 cpufreq_ondemand powernow_k8 freq_table dm_mirror dm_log dm_multipath dm_mod snd_hda_intel snd_seq_dummy sr_mod snd_seq_oss cdrom snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep snd pcspkr serio_raw k8temp hwmon forcedeth soundcore pata_amd sg jedec_probe cfi_probe gen_probe mtd i2c_nforce2 chipreg i2c_core button map_funcs sata_nv ata_generic pata_acpi libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan] Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P 2.6.27-pnfs #1 Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>] [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS: 00010246 Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX: 00000000ffffff95 RCX: 0000000000000000 Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI: ffff88002fc52dc0 RDI: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08: ffff88002f9dae40 R09: ffffffff81489e60 Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11: ffff88002a70bd30 R12: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14: ffff88002f57fa00 R15: ffff88002fc52e50 Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000) GS:ffffffff8148da80(0000) knlGS:0000000000000000 Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3: 000000002f971000 CR4: 00000000000006e0 Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405, threadinfo ffff88002a70a000, task ffff88003694d900) Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000 ffff88002f57fa00 ffff88002fc52dc0 ffff880030450ce8 Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db ffff88002a70bdf0 ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00 ffff880030450ce8 ffff88002a734000 Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>] __rpc_execute+0x7e/0x21f [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>] rpc_execute+0x28/0x2c [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>] rpc_run_bc_task+0x88/0xae [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>] bc_svc_process+0xf6/0x101 [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ? prepare_to_wait+0x5c/0x65 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>] nfs41_callback_svc+0xda/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ? autoremove_wake_function+0x0/0x38 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ? nfs41_callback_svc+0x0/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11 Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ? pick_next_task_fair+0x93/0xa3 Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ? child_rip+0x0/0x11 Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49 c7 44 24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30 e8 b9 2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00 f0 80 a2 Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1225
Quoted 10 lines
net/sunrpc/clnt.c +3
-2@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty)printk ("%s: RPC call returned error %d\n" , - clnt->cl_protname, -status); + clnt ? clnt->cl_protname :"<unknown protocol>" , + -status);
Is this message useful if clnt == NULL?
How would one go about debugging if the message appears with "<unknown protocol>" in it?
Thanx...
ps
Quoted 8 lines
net/sunrpc/clnt.c +0
-0rpc_exit (task, status); }}
_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
Quoted 78 lines · Benny Halevy
On the following error path
task->tk_client== NULL causing NULL deref:Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000078 Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P) panlayoutdriver nfslayoutdriver nfsd auth_rpcgss exportfs nfs lockd nfs_acl fuse sunrpc ipv6 cpufreq_ondemand powernow_k8 freq_table dm_mirror dm_log dm_multipath dm_mod snd_hda_intel snd_seq_dummy sr_mod snd_seq_oss cdrom snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep snd pcspkr serio_raw k8temp hwmon forcedeth soundcore pata_amd sg jedec_probe cfi_probe gen_probe mtd i2c_nforce2 chipreg i2c_core button map_funcs sata_nv ata_generic pata_acpi libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan] Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P 2.6.27-pnfs #1 Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>] [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS: 00010246 Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX: 00000000ffffff95 RCX: 0000000000000000 Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI: ffff88002fc52dc0 RDI: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08: ffff88002f9dae40 R09: ffffffff81489e60 Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11: ffff88002a70bd30 R12: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14: ffff88002f57fa00 R15: ffff88002fc52e50 Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000) GS:ffffffff8148da80(0000) knlGS:0000000000000000 Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3: 000000002f971000 CR4: 00000000000006e0 Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405, threadinfo ffff88002a70a000, task ffff88003694d900) Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000 ffff88002f57fa00 ffff88002fc52dc0 ffff880030450ce8 Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db ffff88002a70bdf0 ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00 ffff880030450ce8 ffff88002a734000 Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>] __rpc_execute+0x7e/0x21f [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>] rpc_execute+0x28/0x2c [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>] rpc_run_bc_task+0x88/0xae [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>] bc_svc_process+0xf6/0x101 [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ? prepare_to_wait+0x5c/0x65 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>] nfs41_callback_svc+0xda/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ? autoremove_wake_function+0x0/0x38 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ? nfs41_callback_svc+0x0/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11 Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ? pick_next_task_fair+0x93/0xa3 Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ? child_rip+0x0/0x11 Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49 c7 44 24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30 e8 b9 2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00 f0 80 a2 Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)rpc_exit (task, status);break ;
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 10 lines
net/sunrpc/clnt.c +3
-2default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty)printk ("%s: RPC call returned error %d\n" , - clnt->cl_protname, -status); + clnt ? clnt->cl_protname :"<unknown protocol>" , + -status);rpc_exit (task, status); } }
BIG NACK!
How does even it make sense for a task to get past call_transmit and call_status without having task->tk_client set? This sounds like serious borkenness in the nfsv4.1 patches...
Trond
...
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULL
deref:
Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULL
pointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)
panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfuse
sunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipath
Quoted 4 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp hwmon forcedeth soundcorepata_amdsgjedec_probecfi_probegen_probe
mtd
Quoted 8 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:
00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95
Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0
Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40
Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30
Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00
Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000
Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:
0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0
Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,
threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00
Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2c
Quoted 12 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
Quoted 9 lines
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 > Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?pick_next_task_fair+0x93/0xa3 > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11
Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49
c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknown
protocol>",
Quoted 9 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitandcall_statuswithout havingtask->tk_clientset? This sounds like
serious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't obtain a pre-allocated rpc_rqst to process the callback. When this occurs, the client sets the XPRT_CLOSE_WAIT bit to close the connection. (As an aside, should we be using xprt_force_disconnect() instead?).
This leads me to believe the server exceeded the number of outstanding requests allowed on the backchannel (slot count of one at the moment), the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
- ricardo
Quoted 5 lines
Trond
...--
To unsubscribe from this list: send the line "unsubscribe linux-nfs"
in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Ricardo:
I don't mean to throw this whole discussion down a rat-hole, but the current back channel architecture isn't transport independent, so NFSRDMA on NFS41 is basically broken because all the back-channel logic is in the xprtsock.c (transport specific) file. It also assumes that the same socket (not transport, socket) is used for both fore and back channel communication.
What are the plans long-term for making this consistent with the existing architecture? Does it have to be the same socket/connection for some reason?
Thanks,
Tom
Quoted 193 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 4 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp hwmon forcedeth soundcorepata_amdsgjedec_probecfi_probegen_probemtd
Quoted 8 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 12 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?Quoted 9 lines
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 > Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?pick_next_task_fair+0x93/0xa3 > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitandcall_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't obtain a pre-allocated
rpc_rqstto process the callback. When this occurs, the client sets theXPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).This leads me to believe the server exceeded the number of outstanding requests allowed on the backchannel (slot count of one at the moment), the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
- ricardo
Quoted 5 lines
Trond
...--
To unsubscribe from this list: send the line "unsubscribe linux-nfs"in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
Hi Tom,
The thinking is that NFSRDMA could initially use a TCP callback channel. We'll implement BIND_CONN_TO_SESSION so that the backchannel does not need to be tied to the forechannel connection. This should address the case where you have NFSRDMA for the forechannel and TCP for the backchannel. BIND_CONN_TO_SESSION is also required to reestablish dropped connections effectively (to avoid losing the reply cache).
We're first trying to get enough of the backchannel functionality implemented to make it useful. We can then build on that. Tom Talpey and I had a brief conversation about what would be needed to implement the backchannel over NFSRDMA some time ago. We didn't see anything inherently wrong with the current approach. Tom mentioned there needs to be some RDMA work during the pre-allocation. It will also need to inspect the RPC direction to determine if it needs to queue the request on the callback service, or proceed as usual with the processing of the request.
- ricardo
Quoted 7 lines
-----Original Message-----
From: Tom Tucker [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 4:44 PM
To: Labiaga, Ricardo
Cc: Trond Myklebust; Benny Halevy; NFS list; pNFS Mailing List
Subject: Re: [pnfs] nfs41: sunrpc: handle clnt==NULL incall_status
Quoted 5 lines
Ricardo:
I don't mean to throw this whole discussion down a rat-hole, but the current back channel architecture isn't transport independent, so NFSRDMA on NFS41 is basically broken because all the back-channel
logic
Quoted 1 line
is in the
xprtsock.c(transport specific) file. It also assumes that
the
Quoted 5 lines
same socket (not transport, socket) is used for both fore and back channel communication.
What are the plans long-term for making this consistent with the existing architecture? Does it have to be the same socket/connection
for
Quoted 34 lines
some reason?
Thanks,
TomQuoted 28 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 3 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_raw
k8temp
Quoted 1 line
Quoted 1 line
Quoted 1 line
hwmon forcedeth soundcore
pata_amdsgjedec_probecfi_probe
gen_probe
Quoted 5 lines
Quoted 5 lines
mtd
Quoted 4 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted:
P
Quoted 57 lines
Quoted 57 lines
Quoted 4 lines
2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 9 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>]
child_rip+0xa/0x11
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?
pick_next_task_fair+0x93/0xa3Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ?
kthread+0x0/0x76
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78
30
Quoted 2 lines
Quoted 2 lines
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00
00
Quoted 44 lines
Quoted 44 lines
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmit
and
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,
the
Quoted 4 lines
Quoted 4 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 5 lines
Quoted 5 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
Quoted 8 lines
Quoted 8 lines
- ricardo
Quoted 5 lines
Trond
...--
To unsubscribe from this list: send the line "unsubscribe
linux-nfs"
Quoted 7 lines
Quoted 7 lines
in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
Quoted 161 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 4 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp hwmon forcedeth soundcorepata_amdsgjedec_probecfi_probegen_probemtd
Quoted 8 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 12 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?Quoted 9 lines
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 > Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?pick_next_task_fair+0x93/0xa3 > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 6 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
Quoted 4 lines
Quoted 2 lines
How does even it make sense for a task to get past
call_transmitandcall_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
Ricardo,
rpc_run_bc_task sets no task_setup_data.rpc_client when calling rpc_new_task. We might be able to use to fore channel rpc client, but
I'm still concerned that using this path for sending the callback replies is wrong.
Quoted 5 lines
The "Callback slot table overflowed" message means we couldn't obtain a pre-allocated
rpc_rqstto process the callback. When this occurs, the client sets theXPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).
could be, but we might be doing the right thing on the client side in this case already.
Quoted 5 lines
This leads me to believe the server exceeded the number of outstanding requests allowed on the backchannel (slot count of one at the moment), the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
We simply got ENOTCONN back (see value of RBX)
Quoted 2 lines
Is this reproducible?
Not yet.
Benny
Quoted 7 lines
- ricardo
Quoted 3 lines
Trond
...
Quoted 90 lines · Peter Staubach
Quoted 76 lines · Benny Halevy
On the following error path
task->tk_client== NULL causing NULL deref:Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000078 Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P) panlayoutdriver nfslayoutdriver nfsd auth_rpcgss exportfs nfs lockd nfs_acl fuse sunrpc ipv6 cpufreq_ondemand powernow_k8 freq_table dm_mirror dm_log dm_multipath dm_mod snd_hda_intel snd_seq_dummy sr_mod snd_seq_oss cdrom snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep snd pcspkr serio_raw k8temp hwmon forcedeth soundcore pata_amd sg jedec_probe cfi_probe gen_probe mtd i2c_nforce2 chipreg i2c_core button map_funcs sata_nv ata_generic pata_acpi libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan] Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted: P 2.6.27-pnfs #1 Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>] [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS: 00010246 Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX: 00000000ffffff95 RCX: 0000000000000000 Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI: ffff88002fc52dc0 RDI: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08: ffff88002f9dae40 R09: ffffffff81489e60 Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11: ffff88002a70bd30 R12: ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14: ffff88002f57fa00 R15: ffff88002fc52e50 Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000) GS:ffffffff8148da80(0000) knlGS:0000000000000000 Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3: 000000002f971000 CR4: 00000000000006e0 Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405, threadinfo ffff88002a70a000, task ffff88003694d900) Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000 ffff88002f57fa00 ffff88002fc52dc0 ffff880030450ce8 Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db ffff88002a70bdf0 ffff88002fc52dc0 Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00 ffff880030450ce8 ffff88002a734000 Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>] __rpc_execute+0x7e/0x21f [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>] rpc_execute+0x28/0x2c [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>] rpc_run_bc_task+0x88/0xae [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>] bc_svc_process+0xf6/0x101 [sunrpc] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ? prepare_to_wait+0x5c/0x65 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>] nfs41_callback_svc+0xda/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ? autoremove_wake_function+0x0/0x38 Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ? nfs41_callback_svc+0x0/0x131 [nfs] Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>] child_rip+0xa/0x11 Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ? pick_next_task_fair+0x93/0xa3 Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ? kthread+0x0/0x76 Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ? child_rip+0x0/0x11 Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49 c7 44 24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78 30 e8 b9 2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00 00 f0 80 a2 Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>] call_status+0xe1/0x145 [sunrpc] Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1225
Quoted 10 lines
net/sunrpc/clnt.c +3
-2@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty)printk ("%s: RPC call returned error %d\n" , - clnt->cl_protname, -status); + clnt ? clnt->cl_protname :"<unknown protocol>" , + -status);Is this message useful if clnt == NULL?
Quoted 2 lines
How would one go about debugging if the message appears with "<unknown protocol>" in it?
The useful information in this message is the value of the otherwise unhandled error and the fact that clnt==NULL. Either shouldn't happen. Anyway, since cl_chatty seems to be 0 by default I thought it's appropriate to follow the default behavior also when clnt==NULL.
Benny
Quoted 14 lines
Thanx... psQuoted 8 lines
net/sunrpc/clnt.c +0
-0rpc_exit (task, status); }}
_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
Hey Ricardo-
Quoted 9 lines · Ricardo
Hi Tom,
The thinking is that NFSRDMA could initially use a TCP callback channel. We'll implement
BIND_CONN_TO_SESSIONso that the backchannel does not need to be tied to the forechannel connection. This should address the case where you have NFSRDMA for the forechannel and TCP for the backchannel.BIND_CONN_TO_SESSIONis also required to reestablish dropped connections effectively (to avoid losing the reply cache).
Quoted 9 lines
We're first trying to get enough of the backchannel functionality implemented to make it useful. We can then build on that. Tom Talpey and I had a brief conversation about what would be needed to implement the backchannel over NFSRDMA some time ago. We didn't see anything inherently wrong with the current approach. Tom mentioned there needs to be some RDMA work during the pre-allocation. It will also need to inspect the RPC direction to determine if it needs to queue the request on the callback service, or proceed as usual with the processing of the request.
Your approach is fine for a prototype. However...
Now we have to have this conversation again when adding any new transport capability, such as SCTP.
Plus, to support NFSv4.1 over RDMA, you now _require_ the existence of an IP network between client and server. This may be as minor as ensuring IPoIB is configured on both ends, but it's still a significant extra step for a pure SAN over RDMA environment. This obviates the whole point of combining the forward and back channels onto one transport.
In my opinion you are making the developer's life simpler now and complicating the lives of current users and admins, and future developers.
Quoted 234 lines
Quoted 7 lines
-----Original Message-----
From: Tom Tucker [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 4:44 PM
To: Labiaga, Ricardo
Cc: Trond Myklebust; Benny Halevy; NFS list; pNFS Mailing List
Subject: Re: [pnfs] nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 5 lines
Ricardo:
I don't mean to throw this whole discussion down a rat-hole, but the current back channel architecture isn't transport independent, so NFSRDMA on NFS41 is basically broken because all the back-channel
logic
Quoted 1 line
is in the
xprtsock.c(transport specific) file. It also assumes thatthe
Quoted 5 lines
same socket (not transport, socket) is used for both fore and back channel communication.
What are the plans long-term for making this consistent with the existing architecture? Does it have to be the same socket/connection
for
Quoted 34 lines
some reason?
Thanks,
TomQuoted 28 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 3 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp
Quoted 1 line
Quoted 1 line
Quoted 1 line
hwmon forcedeth soundcore
pata_amdsgjedec_probecfi_probe
gen_probeQuoted 5 lines
Quoted 5 lines
mtd
Quoted 4 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted:P
Quoted 57 lines
Quoted 57 lines
Quoted 4 lines
2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 9 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>]
child_rip+0xa/0x11Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?
pick_next_task_fair+0x93/0xa3Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ?
kthread+0x0/0x76Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78
30
Quoted 2 lines
Quoted 2 lines
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00
00
Quoted 44 lines
Quoted 44 lines
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c| 8 +++++---1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1223
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitand
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,the
Quoted 4 lines
Quoted 4 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 5 lines
Quoted 5 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
Quoted 8 lines
Quoted 8 lines
- ricardo
Quoted 5 lines
Trond
...--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 7 lines
Quoted 7 lines
in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
Quoted 4 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Quoted 9 lines · Ricardo
Hi Tom,
The thinking is that NFSRDMA could initially use a TCP callback channel. We'll implement
BIND_CONN_TO_SESSIONso that the backchannel does not need to be tied to the forechannel connection. This should address the case where you have NFSRDMA for the forechannel and TCP for the backchannel.BIND_CONN_TO_SESSIONis also required to reestablish dropped connections effectively (to avoid losing the reply cache).
Quoted 10 lines
We're first trying to get enough of the backchannel functionality implemented to make it useful. We can then build on that. Tom Talpey and I had a brief conversation about what would be needed to implement the backchannel over NFSRDMA some time ago. We didn't see anything inherently wrong with the current approach. Tom mentioned there needs to be some RDMA work during the pre-allocation. It will also need to inspect the RPC direction to determine if it needs to queue the request on the callback service, or proceed as usual with the processing of the request.
Thanks for the explanation.
Tom
Quoted 240 lines
- ricardo
Quoted 7 lines
-----Original Message-----
From: Tom Tucker [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 4:44 PM
To: Labiaga, Ricardo
Cc: Trond Myklebust; Benny Halevy; NFS list; pNFS Mailing List
Subject: Re: [pnfs] nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 5 lines
Ricardo:
I don't mean to throw this whole discussion down a rat-hole, but the current back channel architecture isn't transport independent, so NFSRDMA on NFS41 is basically broken because all the back-channel
logic
Quoted 1 line
is in the
xprtsock.c(transport specific) file. It also assumes thatthe
Quoted 5 lines
same socket (not transport, socket) is used for both fore and back channel communication.
What are the plans long-term for making this consistent with the existing architecture? Does it have to be the same socket/connection
for
Quoted 34 lines
some reason?
Thanks,
TomQuoted 28 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 3 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp
Quoted 1 line
Quoted 1 line
Quoted 1 line
hwmon forcedeth soundcore
pata_amdsgjedec_probecfi_probe
gen_probeQuoted 5 lines
Quoted 5 lines
mtd
Quoted 4 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted:P
Quoted 57 lines
Quoted 57 lines
Quoted 4 lines
2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 9 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>]
child_rip+0xa/0x11Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?
pick_next_task_fair+0x93/0xa3Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ?
kthread+0x0/0x76Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78
30
Quoted 2 lines
Quoted 2 lines
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00
00
Quoted 44 lines
Quoted 44 lines
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1223
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitand
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,the
Quoted 4 lines
Quoted 4 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 5 lines
Quoted 5 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
Quoted 8 lines
Quoted 8 lines
- ricardo
Quoted 5 lines
Trond
...--
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 7 lines
Quoted 7 lines
in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 22 lines · Chuck Lever
Hey Ricardo-
Quoted 9 lines · Ricardo
Hi Tom,
The thinking is that NFSRDMA could initially use a TCP callback channel. We'll implement
BIND_CONN_TO_SESSIONso that the backchannel does not need to be tied to the forechannel connection. This should address the case where you have NFSRDMA for the forechannel and TCP for the backchannel.BIND_CONN_TO_SESSIONis also required to reestablish dropped connections effectively (to avoid losing the reply cache).Quoted 9 lines
We're first trying to get enough of the backchannel functionality implemented to make it useful. We can then build on that. Tom Talpey and I had a brief conversation about what would be needed to implement the backchannel over NFSRDMA some time ago. We didn't see anything inherently wrong with the current approach. Tom mentioned there needs to be some RDMA work during the pre-allocation. It will also need to inspect the RPC direction to determine if it needs to queue the request on the callback service, or proceed as usual with the processing of the request.
Quoted 5 lines
Your approach is fine for a prototype. However...
Now we have to have this conversation again when adding any new transport capability, such as SCTP.
Plus, to support NFSv4.1 over RDMA, you now _require_ the existence of an IP network between client and server. This may be as minor as ensuring IPoIB is configured on both ends, but it's still a significant extra step for a pure SAN over RDMA environment.
FWIW, We already require IPoIB because the NFSRDMA implementation uses the RDMA CM which is IP address based.
This obviates the
Quoted 253 lines
whole point of combining the forward and back channels onto one transport.
In my opinion you are making the developer's life simpler now and complicating the lives of current users and admins, and future developers.
Quoted 238 lines
Quoted 7 lines
-----Original Message-----
From: Tom Tucker [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 4:44 PM
To: Labiaga, Ricardo
Cc: Trond Myklebust; Benny Halevy; NFS list; pNFS Mailing List
Subject: Re: [pnfs] nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 5 lines
Ricardo:
I don't mean to throw this whole discussion down a rat-hole, but the current back channel architecture isn't transport independent, so NFSRDMA on NFS41 is basically broken because all the back-channel
logic
Quoted 1 line
is in the
xprtsock.c(transport specific) file. It also assumes thatthe
Quoted 5 lines
same socket (not transport, socket) is used for both fore and back channel communication.
What are the plans long-term for making this consistent with the existing architecture? Does it have to be the same socket/connection
for
Quoted 34 lines
some reason?
Thanks,
TomQuoted 28 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 3 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_rawk8temp
Quoted 1 line
Quoted 1 line
Quoted 1 line
hwmon forcedeth soundcore
pata_amdsgjedec_probecfi_probe
gen_probeQuoted 5 lines
Quoted 5 lines
mtd
Quoted 4 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted:P
Quoted 57 lines
Quoted 57 lines
Quoted 4 lines
2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 9 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>]
child_rip+0xa/0x11Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?
pick_next_task_fair+0x93/0xa3Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ?
kthread+0x0/0x76Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78
30
Quoted 2 lines
Quoted 2 lines
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00
00
Quoted 44 lines
Quoted 44 lines
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c| 8 +++++---1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1223
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitand
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,the
Quoted 4 lines
Quoted 4 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 5 lines
Quoted 5 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
Is this reproducible?
Quoted 8 lines
Quoted 8 lines
- ricardo
Quoted 5 lines
Trond
...Signature · 1 line
To unsubscribe from this list: send the line "unsubscribelinux-nfs"
Quoted 7 lines
Quoted 7 lines
in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html_______________________________________________
pNFS mailing list
[email protected]
http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfsSignature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 9 lines
Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 10 lines · Chuck Lever
Now we have to have this conversation again when adding any new transport capability, such as SCTP.
Plus, to support NFSv4.1 over RDMA, you now _require_ the existence of an IP network between client and server. This may be as minor as ensuring IPoIB is configured on both ends, but it's still a significant extra step for a pure SAN over RDMA environment. This obviates the whole point of combining the forward and back channels onto one transport.
Quoted 3 lines
In my opinion you are making the developer's life simpler now and complicating the lives of current users and admins, and future developers.
Please read what Ricardo said: this is a _first_ approximation, not a final solution. Given what they're hoping to achieve, I'm fine with doing a simple implementation of sessions first, then progressively refining it.
Furthermore, there should be nothing conceptually in his design that prevents you from adapting it to other transports: it is basically just preallocating a buffer, then using that as a receive buffer when you find that you have a callback request.
Trond
Quoted 6 lines · Chuck Lever
Quoted 2 lines · Tom Tucker
FWIW, We already require IPoIB because the NFSRDMA implementation uses the RDMA CM which is IP address based.
Oh, that's too bad. I thought the IP sideband requirement would go away with NFSv4 over RDMA because NLM/NSM would be retired.
Just think of it like ARP. The RDMA CM is a low-level discovery and connection protocol, which isn't actually used by RPC or NFS at all. It just magically comes into play when the RPC client calls into the rdma_connect() subsystem. RDMA uses IP addresses, btw.
Tom.
Quoted 9 lines
-----Original Message-----
From: Benny Halevy [mailto:[email protected]]
Sent: Wednesday, November 05, 2008 5:13 AM
To: Labiaga, Ricardo
Cc: Trond Myklebust; pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_status
Quoted 30 lines
Quoted 28 lines · Ricardo
Quoted 9 lines
-----Original Message-----
From: Trond Myklebust [mailto:[email protected]]
Sent: Tuesday, November 04, 2008 10:19 AM
To: Benny Halevy
Cc: pNFS Mailing List; NFS list
Subject: Re: nfs41: sunrpc: handle clnt==NULL incall_statusQuoted 1 line · Benny Halevy
On the following error path
task->tk_client== NULL causing NULLderef:
Quoted 2 lines
Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Callback slot table overflowed Nov 4 14:14:32 tl1 kernel: BUG: unable to handle kernel NULLpointer
Quoted 7 lines
dereference at 0000000000000078
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: IP: [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 4 lines
Nov 4 14:14:32 tl1 kernel: PGD 2f973067 PUD 2f974067 PMD 0 Nov 4 14:14:32 tl1 kernel: Oops: 0000 [1] SMP Nov 4 14:14:32 tl1 kernel: CPU 0 Nov 4 14:14:32 tl1 kernel: Modules linked in: panfs(P)panlayoutdriver
Quoted 1 line
nfslayoutdriver nfsd
auth_rpcgssexportfs nfs lockdnfs_aclfusesunrpc
Quoted 1 line
ipv6
cpufreq_ondemandpowernow_k8freq_tabledm_mirrordm_log
dm_multipathQuoted 3 lines
dm_modsnd_hda_intelsnd_seq_dummysr_modsnd_seq_osscdromsnd_seq_midi_eventsnd_seqsnd_seq_devicesnd_pcm_osssnd_mixer_osssnd_pcmsnd_timersnd_page_allocsnd_hwdepsnd pcspkrserio_raw
k8temp
Quoted 1 line
Quoted 1 line
Quoted 1 line
hwmon forcedeth soundcore
pata_amdsgjedec_probecfi_probe
gen_probe
Quoted 5 lines
Quoted 5 lines
mtd
Quoted 4 lines
i2c_nforce2chipregi2c_corebuttonmap_funcssata_nvata_genericpata_acpilibatasd_modscsi_modext3 jbd mbcacheuhci_hcdohci_hcdehci_hcd[last unloaded:scsi_wait_scan]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Pid: 3405, comm: nfsv4.1-svc Tainted:
P
Quoted 57 lines
Quoted 57 lines
Quoted 4 lines
2.6.27-pnfs #1
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP: 0010:[<ffffffffa02b4dd2>][<
ffffffffa02b4dd2>]call_status+0xe1/0x145[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RSP: 0018:ffff88002a70bd60 EFLAGS:00010246
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RAX: 0000000000000000 RBX:
00000000ffffff95Quoted 2 lines
RCX: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RDX: ffff88002a70bd10 RSI:
ffff88002fc52dc0Quoted 2 lines
RDI:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RBP: ffff88002a70bd80 R08:
ffff88002f9dae40Quoted 2 lines
R09:
ffffffff81489e60Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R10: ffff880038497800 R11:
ffff88002a70bd30Quoted 2 lines
R12:
ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: R13: 0000000000000000 R14:
ffff88002f57fa00Quoted 6 lines
R15:
ffff88002fc52e50Quoted 1 line
Nov 4 14:14:32 tl1 kernel: FS: 00007fe78ffac6f0(0000)GS:ffffffff8148da80(0000) knlGS:0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003bQuoted 1 line
Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 CR3:
000000002f971000Quoted 2 lines
CR4:
00000000000006e0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR0: 0000000000000000 DR1:0000000000000000
Quoted 2 lines
DR2: 0000000000000000
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0Quoted 2 lines
DR7: 0000000000000400
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Process nfsv4.1-svc (pid: 3405,threadinfo
Quoted 2 lines
ffff88002a70a000, taskffff88003694d900)Quoted 1 line
Nov 4 14:14:32 tl1 kernel: Stack: 0000000000000000
ffff88002f57fa00Quoted 9 lines
ffff88002fc52dc0ffff880030450ce8Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002a70bdc0 ffffffffa02bb9db
ffff88002a70bdf0ffff88002fc52dc0Quoted 1 line
Nov 4 14:14:32 tl1 kernel: ffff88002f57fa00 ffff88002f57fa00
ffff880030450ce8ffff88002a734000Quoted 2 lines
Nov 4 14:14:32 tl1 kernel: Call Trace: Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bb9db>]
__rpc_execute+0x7e/0x21f[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bbba4>]
rpc_execute+0x28/0x2cQuoted 9 lines
[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02b5596>]rpc_run_bc_task+0x88/0xae [sunrpc] > Nov 4 14:14:32 tl1 kernel: [<ffffffffa02c923d>] bc_send+0x35/0x5a[sunrpc]
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa02bdc92>]
bc_svc_process+0xf6/0x101[sunrpc]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048a6c>] ?
prepare_to_wait+0x5c/0x65
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a4c9>]
nfs41_callback_svc+0xda/0x131[nfs]Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff810488a0>] ?
autoremove_wake_function+0x0/0x38Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffffa033a3ef>] ?nfs41_callback_svc+0x0/0x131 [nfs] > Nov 4 14:14:32 tl1 kernel: [<ffffffff81048561>] kthread+0x49/0x76Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf49>]
child_rip+0xa/0x11
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8102a401>] ?
pick_next_task_fair+0x93/0xa3Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff81048518>] ?
kthread+0x0/0x76
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: [<ffffffff8100cf3f>] ?
child_rip+0x0/0x11Quoted 3 lines
Quoted 3 lines
Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Nov 4 14:14:32 tl1 kernel: Code: e8 7c 70 00 00 49 8b 44 24 20 49c7 44
Quoted 1 line
24 68 dc 48 2b a0 f6 40 78 02 74 6d 41 8b b6 34 01 00 00 48 8b 78
30
Quoted 2 lines
Quoted 2 lines
e8 b9
Quoted 1 line
2a 00 00 eb 5b <41> f6 45 78 04 74 13 49 8b 55 30 48 8d 82 80 04 00
00
Quoted 44 lines
Quoted 44 lines
f0
Quoted 34 lines
80 a2
Quoted 1 line
Nov 4 14:14:32 tl1 kernel: RIP [<ffffffffa02b4dd2>]
call_status+0xe1/0x145[sunrpc]Quoted 31 lines
Nov 4 14:14:32 tl1 kernel: RSP <ffff88002a70bd60> Nov 4 14:14:32 tl1 kernel: CR2: 0000000000000078 Nov 4 14:14:32 tl1 kernel: ---[ end trace 1584c489f2573aaf ]---Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task)
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmit
and
Quoted 9 lines
Quoted 3 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
Ricardo,
rpc_run_bc_tasksets no task_setup_data.rpc_client when callingrpc_new_task.
We might be able to use to fore channel rpc client,
We could, though it would cause the reconnection to occur in the backchannel code path. Haven't thought it through, but it sounds cleaner to rebind the session (or reset it if the server went away) in the forechannel context. I wonder if it would be acceptable to simply drop the backchannel request, and have the forechannel reestablish the connection (on a retransmission)?
Quoted 3 lines
but
I'm still concerned that using this path for sending the callback replies is wrong.
The mainline RPC call_transmit() is already able to deal with RPC transmissions that don't expect a reply. This is pretty similar to sending a reply, so we're leveraging the existing rpc_xprt.
One alternative could be to construct an svc_xprt for the backchannel and use svc_send() for the reply. I wonder if it's really a better approach since we already have the rpc_xprt available.
Quoted 2 lines
Quoted 2 lines
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,
the
Quoted 5 lines
Quoted 2 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).could be, but we might be doing the right thing on the client side in this case already.
We're correctly closing the connection, but doesn't seem like we're acquiring the lock, as it is done in xprt_force_disconnect(). xprt_force_disconnect() wasn't around when I first added the autoclose code in xs_tcp_read_callback().
Quoted 3 lines
Quoted 3 lines
This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 4 lines
Quoted 2 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
We simply got ENOTCONN back (see value of RBX)
Right, I was trying to explain what may have caused the connection closed error. I'm suggesting the unexpected request closed the connection, and was dropped on the floor by xs_tcp_read_callback(). After the first request was processed, it encountered a closed connection during the reply. This is why the original request dies with ENOTCONN.
I'll take a look at the svc_send() path using svc_xprt. Though I think your proposed patch to not force a rebind in the backchannel is appropriate. I guess I'm pleading to Trond to reconsider the Big NACK :-)
- ricardo
Quoted 15 lines
Quoted 3 lines
Is this reproducible?
Not yet.
Benny
Quoted 7 lines
- ricardo
Quoted 3 lines
Trond
...
Quoted 66 lines · Ricardo
Quoted 37 lines
Quoted 37 lines
Quoted 28 lines
Quoted 28 lines
Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c| 8 +++++---1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1223
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitand
Quoted 9 lines
Quoted 3 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
Ricardo,
rpc_run_bc_tasksets no task_setup_data.rpc_client when callingrpc_new_task.
We might be able to use to fore channel rpc client,We could, though it would cause the reconnection to occur in the backchannel code path. Haven't thought it through, but it sounds cleaner to rebind the session (or reset it if the server went away) in the forechannel context. I wonder if it would be acceptable to simply drop the backchannel request, and have the forechannel reestablish the connection (on a retransmission)?
Quoted 3 lines
but
I'm still concerned that using this path for sending the callback replies is wrong.
Quoted 7 lines
The mainline RPC
call_transmit()is already able to deal with RPC transmissions that don't expect a reply. This is pretty similar to sending a reply, so we're leveraging the existingrpc_xprt.One alternative could be to construct an
svc_xprtfor the backchannel and usesvc_send()for the reply. I wonder if it's really a better approach since we already have therpc_xprtavailable.
I failed to mention that with the existing approach we're able to synchronize forechannel calls and backchannel replies on the rpc_xprt (XPRT_LOCKED bit). It uses the synchronization mechanism already in mainline to prevent mixing the payload of requests and replies.
- ricardo
Quoted 57 lines
Quoted 3 lines
Quoted 3 lines
The "Callback slot table overflowed" message means we couldn't
obtain a
Quoted 1 line
Quoted 1 line
pre-allocated
rpc_rqstto process the callback. When this occurs,the
Quoted 5 lines
Quoted 2 lines
client sets the
XPRT_CLOSE_WAITbit to close the connection. (As an aside, should we be usingxprt_force_disconnect()instead?).could be, but we might be doing the right thing on the client side in this case already.
We're correctly closing the connection, but doesn't seem like we're acquiring the lock, as it is done in
xprt_force_disconnect().xprt_force_disconnect()wasn't around when I first added the autoclose code inxs_tcp_read_callback().Quoted 3 lines
Quoted 3 lines
This leads me to believe the server exceeded the number of
outstanding
Quoted 1 line
Quoted 1 line
requests allowed on the backchannel (slot count of one at the
moment),
Quoted 4 lines
Quoted 2 lines
the new request caused us to close the connection and pulled the rug from under the callback service. I'll investigate further.
We simply got ENOTCONN back (see value of RBX)
Right, I was trying to explain what may have caused the connection closed error. I'm suggesting the unexpected request closed the connection, and was dropped on the floor by
xs_tcp_read_callback(). After the first request was processed, it encountered a closed connection during the reply. This is why the original request dies with ENOTCONN.I'll take a look at the
svc_send()path usingsvc_xprt. Though I think your proposed patch to not force a rebind in the backchannel is appropriate. I guess I'm pleading to Trond to reconsider the Big NACK :-)- ricardo
Quoted 15 lines
Quoted 3 lines
Is this reproducible?
Not yet.
Benny
Quoted 7 lines
- ricardo
Quoted 3 lines
Trond
...
Quoted 68 lines · Ricardo Labiaga
Quoted 66 lines · Ricardo
Quoted 36 lines
Quoted 36 lines
Quoted 27 lines
Quoted 27 lines
Signed-off-by Benny Halevy <[email protected]>---
Trond, I'm not sure if this can happen without nfs41. However, please consider this patch for upstream since it is safe to do in any case.
Benny
net/sunrpc/clnt.c| 8 +++++---1 files changed, 5 insertions(+), 3 deletions(-)net/sunrpc/clnt.c +2
-1@@ -1206,7 +1206,8 @@ call_status(struct rpc_task *task)break ;case -ECONNREFUSED :case -ENOTCONN : -rpc_force_rebind (clnt); +if (clnt) +rpc_force_rebind (clnt); task->tk_action = call_bind;break ;case -EAGAIN :@@ -1217,9 +1218,10 @@ call_status(struct rpc_task *task)Quoted 8 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1223
Quoted 8 lines
net/sunrpc/clnt.c +2
-2rpc_exit (task, status);break ;default : -if (clnt->cl_chatty) +if (!clnt || clnt->cl_chatty) printk("%s: RPC call returned error %d\n", - clnt->cl_protname, -status); + clnt ? clnt->cl_protname : "<unknownprotocol>",
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
net/sunrpc/clnt.c call_status(struct rpc_task *task) · line 1227
Quoted 4 lines
net/sunrpc/clnt.c +1
-0+ -status);rpc_exit (task, status); } }BIG NACK!
How does even it make sense for a task to get past
call_transmitand
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
call_statuswithout havingtask->tk_clientset? This sounds likeserious
Quoted 1 line
borkenness in the nfsv4.1 patches...
Ricardo,
rpc_run_bc_tasksets no task_setup_data.rpc_client when callingrpc_new_task.
We might be able to use to fore channel rpc client,We could, though it would cause the reconnection to occur in the backchannel code path. Haven't thought it through, but it sounds cleaner to rebind the session (or reset it if the server went away) in the forechannel context. I wonder if it would be acceptable to simply drop the backchannel request, and have the forechannel reestablish the connection (on a retransmission)?
Quoted 3 lines
but
I'm still concerned that using this path for sending the callback replies is wrong.The mainline RPC
call_transmit()is already able to deal with RPC transmissions that don't expect a reply. This is pretty similar to sending a reply, so we're leveraging the existingrpc_xprt.
Quoted 8 lines
Quoted 3 lines
One alternative could be to construct an
svc_xprtfor the backchannel and usesvc_send()for the reply. I wonder if it's really a better approach since we already have therpc_xprtavailable.I failed to mention that with the existing approach we're able to synchronize forechannel calls and backchannel replies on the
rpc_xprt(XPRT_LOCKEDbit). It uses the synchronization mechanism already in mainline to prevent mixing the payload of requests and replies.
Right, but we need to do this at the xprt layer. I don't think that this mandates starting the reply process from the rpc layer as we do today in bc_send.
Note that bc_svc_process gets both an rpc_rqst and a svc_rqst. Although we forge a svc_rqst including setting up its rq_xprt which is a svc_xprt, I'm not sure what exactly it is used for. Eventually, we end up sending the reply (via bc_send) using the rpc_rqst and its associated rpc_xprt. This will allow us to synchronize properly on the bi-directional channel.
Quoted 3 lines
- ricardo
[snip]
Quoted 1 line
From: Benny Halevy [mailto:[email protected]]
[snip]
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Ricardo,
rpc_run_bc_tasksets no task_setup_data.rpc_client when callingrpc_new_task.
We might be able to use to fore channel rpc client,We could, though it would cause the reconnection to occur in the backchannel code path. Haven't thought it through, but it sounds cleaner to rebind the session (or reset it if the server went away)
in
Quoted 1 line
Quoted 1 line
Quoted 1 line
the forechannel context. I wonder if it would be acceptable to
simply
Quoted 1 line
Quoted 1 line
Quoted 1 line
drop the backchannel request, and have the forechannel reestablish
the
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
connection (on a retransmission)?
Quoted 3 lines
but
I'm still concerned that using this path for sending the callback replies is wrong.The mainline RPC
call_transmit()is already able to deal with RPC transmissions that don't expect a reply. This is pretty similar to sending a reply, so we're leveraging the existingrpc_xprt.One alternative could be to construct an
svc_xprtfor the
backchannel
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
and use
svc_send()for the reply. I wonder if it's really a better approach since we already have therpc_xprtavailable.I failed to mention that with the existing approach we're able to synchronize forechannel calls and backchannel replies on the
rpc_xprt
Quoted 10 lines
Quoted 2 lines
(
XPRT_LOCKEDbit). It uses the synchronization mechanism already in mainline to prevent mixing the payload of requests and replies.Right, but we need to do this at the xprt layer. I don't think that this mandates starting the reply process from the rpc layer as we do today in
bc_send.Note that
bc_svc_processgets both anrpc_rqstand asvc_rqst. Although we forge asvc_rqstincluding setting up itsrq_xprtwhich is asvc_xprt, I'm not sure what exactly it is used for.
Correct, we build the svc_rqst so that we can use it in the processing of the backchannel request. This way we reuse all of the existing v4 backchannel logic for decoding, authenticating, dispatching, and result checking in svc_process_common().
Quoted 3 lines
Eventually, we end up sending the reply (via
bc_send) using therpc_rqstand its associatedrpc_xprt. This will allow us to synchronize properly on the bi-directional channel.
If we really want to avoid the RPC state machine, I guess we could first serialize on the rpc_rqst by calling test_and_set_bit(XPRT_LOCKED, &xprt->state) to ensure no outgoing RPC grabs the transport. We then issue the reply using svc_send() with the svc_rqst. This does avoid having to copy the send buffer into the rpc_rqst, avoid building an rpc_task, and avoid entering the RPC state machine, though it requires an extra synchronization on the svc_xprt.xpt_mutex.
Is this along the lines of what you're thinking? I can give it a try...
- ricardo
Quoted 6 lines
Quoted 4 lines
- ricardo
[snip]
Quoted 58 lines
From: Labiaga, Ricardo [mailto:[email protected]]
Quoted 1 line
From: Benny Halevy [mailto:[email protected]]
[snip]
Quoted 28 lines
Quoted 19 lines
Quoted 9 lines
Quoted 5 lines
Ricardo,
rpc_run_bc_tasksets no task_setup_data.rpc_client when callingrpc_new_task.
We might be able to use to fore channel rpc client,We could, though it would cause the reconnection to occur in the backchannel code path. Haven't thought it through, but it sounds cleaner to rebind the session (or reset it if the server went away) in the forechannel context. I wonder if it would be acceptable to simply
drop the backchannel request, and have the forechannel reestablish the
Quoted 9 lines
connection (on a retransmission)?
Quoted 3 lines
but
I'm still concerned that using this path for sending the callback replies is wrong.The mainline RPC
call_transmit()is already able to deal with RPC transmissions that don't expect a reply. This is pretty similar to sending a reply, so we're leveraging the existingrpc_xprt.Quoted 8 lines
Quoted 3 lines
One alternative could be to construct an
svc_xprtfor the backchannel and usesvc_send()for the reply. I wonder if it's really a better approach since we already have therpc_xprtavailable.I failed to mention that with the existing approach we're able to synchronize forechannel calls and backchannel replies on the
rpc_xprt(XPRT_LOCKEDbit). It uses the synchronization mechanism already in mainline to prevent mixing the payload of requests and replies.Quoted 7 lines
Right, but we need to do this at the xprt layer. I don't think that this mandates starting the reply process from the rpc layer as we do today in
bc_send.Note that
bc_svc_processgets both anrpc_rqstand asvc_rqst. Although we forge asvc_rqstincluding setting up itsrq_xprtwhich is asvc_xprt, I'm not sure what exactly it is used for.Correct, we build the
svc_rqstso that we can use it in the processing of the backchannel request. This way we reuse all of the existing v4 backchannel logic for decoding, authenticating, dispatching, and result checking insvc_process_common().Quoted 3 lines
Eventually, we end up sending the reply (via
bc_send) using therpc_rqstand its associatedrpc_xprt. This will allow us to synchronize properly on the bi-directional channel.If we really want to avoid the RPC state machine, I guess we could first serialize on the
rpc_rqstby callingtest_and_set_bit(XPRT_LOCKED, &xprt->state)to ensure no outgoing RPC grabs the transport. We then issue the reply usingsvc_send()with thesvc_rqst. This does avoid having to copy the send buffer into therpc_rqst, avoid building anrpc_task, and avoid entering the RPC state machine, though it requires an extra synchronization on the svc_xprt.xpt_mutex.
Quoted 1 line
Is this along the lines of what you're thinking? I can give it a try...
Yes, absolutely. One thing that came to me is that is would make sense to encapsulate the xprt synchronization primitives in a few helper functions implemnted at the xprt layer so that we won't have to expose the internal implementation to the caller...
Benny
Quoted 3 lines
- ricardo