IJ34824: CRASH OCCURRED WHEN NFS4_ACL_RELEASE_ENTRY() CALLED HASHTABLE_GETLATCH()

APAR status

• Closed as program error.

Error description

• Ganesha process crashed with below stack trace.
  (gdb) bt
  #0 raise (sig=11)
  #1 0x0000000000443529 in crash_handler
  (signo=11, info=0x7f7a4cdc7570, ctx=0x7f7a4cdc7440)
  #2 <signal handler called>
  #3 0x000000000052ac40 in UNALIGNED_LOAD64
  (p=0x4b58c4218 <error: Cannot access memory at
  address 0x4b58c4218>)
  #4 0x000000000052ac7b in Fetch64 (p=0x4b58c4218
  <error: Cannot access memory at address 0x4b58c4218>)
  #5 0x000000000052b46c in CityHash64
  (s=0x0, len=20225737280)
  #6 0x00000000004fe949 in fsal_acl_hash_both
  (hparam=0x1c81700, key=0x7f7a4cdca2e0,
  index=0x7f7a4cdca264, rbthash=0x7f7a4cdca250)
  #7 0x00000000004f1f5a in compute (ht=0x1c81700,
  key=0x7f7a4cdca2e0, index=0x7f7a4cdca264,
  rbt_hash=0x7f7a4cdca250)
  #8 0x00000000004f2946 in hashtable_getlatch
  (ht=0x1c81700, key=0x7f7a4cdca2e0, val=0x7f7a4cdca2c0,
  may_write=true, latch=0x7f7a4cdca2a0)
  #9 0x00000000004ff415 in nfs4_acl_release_entry
  (acl=0x7f7e3c005600)
  #10 0x000000000053cda2 in fsal_release_attrs
  ...
  

Local fix

Problem summary

• Ganesha process crashed with below stack trace.
  (gdb) bt
  #0 raise (sig=11)
  #1 0x0000000000443529 in crash_handler
  (signo=11, info=0x7f7a4cdc7570, ctx=0x7f7a4cdc7440)
  #2 <signal handler called>
  #3 0x000000000052ac40 in UNALIGNED_LOAD64
  (p=0x4b58c4218 <error: Cannot access memory at
  address 0x4b58c4218>)
  #4 0x000000000052ac7b in Fetch64 (p=0x4b58c4218
  <error: Cannot access memory at address 0x4b58c4218>)
  #5 0x000000000052b46c in CityHash64
  (s=0x0, len=20225737280)
  #6 0x00000000004fe949 in fsal_acl_hash_both
  (hparam=0x1c81700, key=0x7f7a4cdca2e0,
  index=0x7f7a4cdca264, rbthash=0x7f7a4cdca250)
  #7 0x00000000004f1f5a in compute (ht=0x1c81700,
  key=0x7f7a4cdca2e0, index=0x7f7a4cdca264,
  rbt_hash=0x7f7a4cdca250)
  #8 0x00000000004f2946 in hashtable_getlatch
  (ht=0x1c81700, key=0x7f7a4cdca2e0, val=0x7f7a4cdca2c0,
  may_write=true, latch=0x7f7a4cdca2a0)
  #9 0x00000000004ff415 in nfs4_acl_release_entry
  (acl=0x7f7e3c005600)
  #10 0x000000000053cda2 in fsal_release_attrs
  

Problem conclusion

• This problem is fixed in 5.0.5  PTF 2
  To see all Spectrum Scale APARs and
  their respective fix solutions refer to page
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  Benefits of the solution:
  Fixed the refcount leak in ganesha.
  Work Around:     None
  Problem trigger:
  The issue mostly occurs when the system is loaded
  with heavy workloads.
  Symptom: Abend/Crash
  Platforms affected: Linux Only
  Functional Area affected: NFS
  Customer Impact: High Importance
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels