I created a centos 6 nfsv4 server, and went through the above recreate procedure with a trusty guest, and could successfully mount, and do file operations with accton. However after a few minutes, the console hung, and most tasks reported the following stack traces in /var/log/kern.log
I then went and installed keyutils and retested, and could not reproduce the hung tasks. At first look this looks to be the endpoint for request_key_and_link out of the kernel. I will verify this tomorrow, and
I created a centos 6 nfsv4 server, and went through the above recreate procedure with a trusty guest, and could successfully mount, and do file operations with accton. However after a few minutes, the console hung, and most tasks reported the following stack traces in /var/log/kern.log
INFO: task ls:2101 blocked for more than 120 seconds. kernel/ hung_task_ timeout_ secs" disables this message. 0ce0>] ? umh_keys_ init+0x20/ 0x20 8499>] schedule+0x29/0x70 0cee>] key_wait_ bit+0xe/ 0x20 8c42>] __wait_ on_bit+ 0x62/0x90 0ce0>] ? umh_keys_ init+0x20/ 0x20 8ce7>] out_of_ line_wait_ on_bit+ 0x77/0x90 b3d0>] ? autoremove_ wake_function+ 0x40/0x40 10be>] wait_for_ key_constructio n+0x6e/ 0x80 160c>] request_ key+0x5c/ 0xa0 858f>] nfs_idmap_ get_key+ 0xaf/0x1c0 [nfsv4] 8f8f>] nfs_map_ name_to_ uid+0xef/ 0x150 [nfsv4] 0117>] decode_ getfattr_ attrs+0xe47/ 0x14b0 [nfsv4] bc79>] ? sched_clock+ 0x9/0x10 080c>] decode_ getfattr_ generic. constprop. 102+0x8c/ 0xf0 [nfsv4] 0ef0>] ? nfs4_xdr_ dec_access+ 0xa0/0xa0 [nfsv4] 0f60>] nfs4_xdr_ dec_getattr+ 0x70/0x80 [nfsv4] e316>] rpcauth_ unwrap_ resp+0x86/ 0xd0 [sunrpc] 0ef0>] ? nfs4_xdr_ dec_access+ 0xa0/0xa0 [nfsv4] 0f6f>] call_decode+ 0x1df/0x870 [sunrpc] 0d90>] ? call_refreshres ult+0x170/ 0x170 [sunrpc] 0d90>] ? call_refreshres ult+0x170/ 0x170 [sunrpc] bd84>] __rpc_execute+ 0x84/0x400 [sunrpc] ccfe>] rpc_execute+ 0x5e/0xa0 [sunrpc] 31d0>] rpc_run_ task+0x70/ 0x90 [sunrpc] 9646>] nfs4_call_ sync_sequence+ 0x56/0x80 [nfsv4] 9f2e>] _nfs4_proc_ getattr+ 0xbe/0xd0 [nfsv4] 04ea>] nfs4_proc_ getattr+ 0x5a/0xd0 [nfsv4] 19df>] __nfs_revalidat e_inode+ 0xbf/0x310 [nfs] 9af3>] nfs_opendir+ 0xe3/0x100 [nfs] b883>] do_dentry_ open+0x233/ 0x2e0 9a10>] ? nfs_readdir_ clear_array+ 0x70/0x70 [nfs] bbb9>] vfs_open+0x49/0x50 cf64>] do_last+ 0x564/0x1240 ac06>] ? link_path_ walk+0x256/ 0x880 615b>] ? apparmor_ file_alloc_ security+ 0x5b/0x180 8786>] ? security_ file_alloc+ 0x16/0x20 dcfb>] path_openat+ 0xbb/0x650 f0fa>] do_filp_ open+0x3a/ 0x90 199e>] ? do_mmap_ pgoff+0x34e/ 0x3d0 bf77>] ? __alloc_ fd+0xa7/ 0x130 d6d9>] do_sys_ open+0x129/ 0x280 05ba>] ? do_page_ fault+0x1a/ 0x70 d864>] SyS_openat+ 0x14/0x20 4c5d>] system_ call_fastpath+ 0x1a/0x1f
Not tainted 3.13.0-66-generic #108-Ubuntu
"echo 0 > /proc/sys/
ls D ffff88007fd13180 0 2101 1215 0x00000004
ffff88007b14d630 0000000000000086 ffff8800374e6000 ffff88007b14dfd8
0000000000013180 0000000000013180 ffff8800374e6000 ffff88007b14d6b0
ffff88007ffd1460 0000000000000002 ffffffff812d0ce0 ffff88007b14d6a0
Call Trace:
[<ffffffff812d
[<ffffffff8172
[<ffffffff812d
[<ffffffff8172
[<ffffffff812d
[<ffffffff8172
[<ffffffff810a
[<ffffffff812d
[<ffffffff812d
[<ffffffffa027
[<ffffffffa027
[<ffffffffa027
[<ffffffff8101
[<ffffffffa027
[<ffffffffa027
[<ffffffffa027
[<ffffffffa013
[<ffffffffa027
[<ffffffffa013
[<ffffffffa013
[<ffffffffa013
[<ffffffffa013
[<ffffffffa013
[<ffffffffa013
[<ffffffffa025
[<ffffffffa025
[<ffffffffa026
[<ffffffffa01e
[<ffffffffa01d
[<ffffffff811b
[<ffffffffa01d
[<ffffffff811b
[<ffffffff811c
[<ffffffff811c
[<ffffffff8131
[<ffffffff812d
[<ffffffff811c
[<ffffffff811c
[<ffffffff8118
[<ffffffff811d
[<ffffffff811b
[<ffffffff8173
[<ffffffff811b
[<ffffffff8173
I then went and installed keyutils and retested, and could not reproduce the hung tasks. At first look this looks to be the endpoint for request_ key_and_ link out of the kernel. I will verify this tomorrow, and
I will look at fixing the dependency tomorrow.
Thank you,