kernel-packages team mailing list archive

[Dave Chiluk <1509120@xxxxxxxxxxxxxxxxxx>]

I also completed the same test as Chris above, without failure.  I was
using Ubuntu trusty+3.13 as the server and Trusty +3.19 as the guest.
At the moment I don't see any reason to assume that there is anything
power specific in this issue, so I attempted on purely x86_64 hardware.

Also can we get the output of the mount command from the client so we
can see verify that all /etc/fstab options were respected?  It's
possible that mount options were passed to the server, but were overrode
by server capability bits.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509120

Title:
  Process accounting deadlock with idmapd callout when writing to NFSv4
  mount

Status in linux package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  System hang when process accounting to a NFSv4 mount.

  ---uname output---
  Linux ppc001 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52
  UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

  ---Problem Details---

  We have a customer that is experiencing intermittent system hangs on
  their system.  After a bit of debug, it was discovered that the
  trigger was turning on process accounting and writing to a file hosted
  via an NFSv4 mount.  During the testing, several vmcores were
  captured, and the fingerprint indicates a mutex deadlock situation
  with process accounting.   In the most recent vmcore, it appears that
  the scenario is something like the following:

  1. PID: 4898 COMMAND: "ls" triggers a write to the process accounting file.
  2. The resulting NFS write needs idmapd information and calls out to idmapd
  3. The idmapd usermodehelper process triggers another process accounting update that blocks on the mutex being held by PID 4898.

  PID: 4898   TASK: c000001fd26d7580  CPU: 7   COMMAND: "ls"
   #0 [c000001fd274a950] __switch_to at c000000000015934
   #1 [c000001fd274ab20] __switch_to at c000000000015934
   #2 [c000001fd274ab80] __schedule at c000000000a11de8
   #3 [c000001fd274ada0] schedule_timeout at c000000000a16284
   #4 [c000001fd274ae90] wait_for_common at c000000000a1360c
   #5 [c000001fd274af10] call_usermodehelper_exec at c0000000000ccd38
   #6 [c000001fd274af70] call_sbin_request_key at c000000000429258
   #7 [c000001fd274b100] request_key_and_link at c00000000042983c
   #8 [c000001fd274b200] request_key at c000000000429978
   #9 [c000001fd274b240] nfs_idmap_get_key at d00000002ca8b0bc [nfsv4]
  #10 [c000001fd274b2b0] nfs_map_name_to_uid at d00000002ca8bbd0 [nfsv4]
  #11 [c000001fd274b320] decode_getfattr_attrs at d00000002ca7f59c [nfsv4]
  #12 [c000001fd274b420] decode_getfattr_generic.constprop.96 at d00000002ca7fd78 
  [nfsv4]
  #13 [c000001fd274b4d0] nfs4_xdr_dec_getattr at d00000002ca80738 [nfsv4]
  #14 [c000001fd274b530] rpcauth_unwrap_resp at d00000001fe67180 [sunrpc]
  #15 [c000001fd274b600] call_decode at d00000001fe527c8 [sunrpc]
  #16 [c000001fd274b6b0] __rpc_execute at d00000001fe64260 [sunrpc]
  #17 [c000001fd274b790] rpc_run_task at d00000001fe54a78 [sunrpc]
  #18 [c000001fd274b7c0] nfs4_call_sync_sequence at d00000002ca60960 [nfsv4]
  #19 [c000001fd274b860] _nfs4_proc_getattr at d00000002ca6217c [nfsv4]
  #20 [c000001fd274b930] nfs4_proc_getattr at d00000002ca6f494 [nfsv4]
  #21 [c000001fd274b9a0] __nfs_revalidate_inode at d0000000202cf614 [nfs]
  #22 [c000001fd274ba30] nfs_revalidate_file_size at d0000000202c9618 [nfs]
  #23 [c000001fd274ba70] nfs_file_write at d0000000202cabdc [nfs]
  #24 [c000001fd274bb00] new_sync_write at c0000000002b3d9c
  #25 [c000001fd274bbd0] __kernel_write at c0000000002b3fec
  #26 [c000001fd274bc20] do_acct_process at c000000000166b78
  #27 [c000001fd274bcc0] acct_process at c00000000016748c
  #28 [c000001fd274bcf0] do_exit at c0000000000b3660
  #29 [c000001fd274bdc0] do_group_exit at c0000000000b3b14
  #30 [c000001fd274be00] sys_exit_group at c0000000000b3bdc
  #31 [c000001fd274be30] system_call at c000000000009258

  PID: 4900   TASK: c000003c9946c180  CPU: 16  COMMAND: "kworker/u320:2"
   #0 [c000003c994fb790] __switch_to at c000000000015934
   #1 [c000003c994fb960] __switch_to at c000000000015934
   #2 [c000003c994fb9c0] __schedule at c000000000a11de8
   #3 [c000003c994fbbe0] schedule_preempt_disabled at c000000000a12980
   #4 [c000003c994fbc00] __mutex_lock_slowpath at c000000000a14aec
   #5 [c000003c994fbc80] mutex_lock at c000000000a14c4c
   #6 [c000003c994fbcb0] acct_get at c0000000001663ec
   #7 [c000003c994fbcf0] acct_process at c000000000167480
   #8 [c000003c994fbd20] do_exit at c0000000000b3660
   #9 [c000003c994fbdf0] ____call_usermodehelper at c0000000000ccaf4
  #10 [c000003c994fbe30] ret_from_kernel_thread at c00000000000956c

  Historical bug data:

  from customer:

   am uploading a crash dump file from a lock up event that I just had.
  I was reminded on a status update call this morning that I never tried
  running process accounting since opening the ticket and updating the
  kernel. So, I tried that this morning. The first time I turned it on
  with the default output location and didn?t have any problems. Then I
  tried turning it on with the output going to our shared disk space,
  which is where I was originally sending it. I ran a couple commands
  that returned just fine, then when I ran a CUDA test program it didn?t
  return and I verified that I was no longer able to login to the node.
  I let it sit for awhile and eventually the console spit out some hung
  process errors. I waited a little longer, but then went ahead and hit
  the key combo to force a dump. I will do some more testing, but right
  now it looks like the problem is running Linux process account
  (accton) with the output directed at an NFS mount. This is the output
  of /proc/mounts for the mount point that I was pointing the output:

  172.17.0.1:/gpfs/sb /gpfs/sb nfs4
  rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.17.12.1,local_lock=none,addr=172.17.0.1
  0 0

  The file system is GPFS 3.5 on the back end, but the client is
  mounting it via NFS. I will try to reproduce the problem on a disk
  that is local to the NFS server just to take the GPFS part out of the
  equation. Our x86 clients are all doing this to directly mounted GPFS
  volumes so I doubt that is the issue.

  Let me know if there is anything else you?d like to see or have me
  try.

  Mike

  == Comment: #21  - 2015-10-19 14:35:35 ==
  I have repeated the problem and narrowed it down to NFS v4. I used an existing NFS export and mounted it with the default options which used NFS v3 and I was unable to get the problem to happen. I then setup an NFS v4 export, mounted that, turned on process accounting to write to that mount point, did an ls. The ls returned data, but the command prompt never returned. After some time I got the standard hung_task error. 

  Mike

  == Comment: #27 - 2015-10-20 15:57:47 ==
  Kevin,
  1. The server is running CentOS 6.x (Most packages are from 6.6). 
  The kernel is 2.6.32-358.18.1.el6.x86_64

  2. This is the /etc/exports line for this directory: 
  /var/psacct 172.17.0.0/16(rw,no_root_squash,sync,fsid=299)

  3. The base FS is ext4. This is its /proc/mounts entry: 
  /dev/md124 /var ext4 rw,relatime,barrier=1,data=ordered 0 0

  4. The clients /etc/fstab looks like this:
  172.17.0.1:/var/psacct/ /mnt    nfs     rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,minorversion=0,local_lock=none      0       0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120/+subscriptions