IJ39626: MAKE GPFS ACL HANDLING ROBUST ON WINDOWS BY EXAMINING ACL ENTRIES IN ADDITION TO VARIOUS FLAGS.

APAR status

• Closed as program error.

Error description

• Not all ACL update interfaces understand
  and preserve the rich Windows ACL flags that
  only get set via native Windows ACL
  interfaces such as icacls or Explorer GUI.
  For example, mmputacl on any supported
  platform could clobber these flags.
  Hence, even if the ACL-flags are somehow blank,
  there still might be a valid ACL.
  

Local fix

Problem summary

• Not all ACL update interfaces understand
  and preserve the rich Windows ACL flags that
  only get set via native Windows ACL
  interfaces such as icacls or Explorer GUI.
  For example, mmputacl on any supported
  platform could clobber these flags.
  Hence, even if the ACL-flags are somehow blank,
  there still might be a valid ACL.
  

Problem conclusion

• This problem is fixed in 5.1.2.5
  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:
  Make GPFS ACL handling code robust by
  examining the existence of a valid ACL instead
  of simply relying on the presence of rich ACL flags.
  
  Work Around:
  None.
  Problem trigger:
  GPFS ACL updates (like mmputacl, mmeditacl etc)
  that do not preserve the
  rich Windows ACL flags.
  Symptom:
  Unexpected Results/Behavior.
  Platforms affected: Windows/x86_64 only.
  Functional Area affected: Authentication/ACLs.
  Customer Impact: Suggested.
  

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