[LU-4746] Lustre not using kernel current_umask() function breaks GRSecurity umask handling

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.7.0
• Affects Version/s: Lustre 2.1.5, Lustre 1.8.9, Lustre 2.5.0, Lustre 2.4.2
• Labels: patch
• Severity: 3
• Assignee: Bob Glossman (Inactive)
• Reporter: Andrew Prout

Description

Lustre 2.5.0 (and before) do not use the kernel's default current_umask() function, instead accessing the current process pointer directly with current->fs->umask. On a standard kernel this is equivalent, however on a GRSecurity-enabled kernel there's additional logic in the kernel's current_umask() function that's being skipped.