[YARN-2847] Linux native container executor segfaults if default banned user detected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0, 2.4.1, 2.6.0
• Fix Version/s: 2.7.0
• Component/s: nodemanager
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Olaf Flebbe
• Reporter: Jason Darrell Lowe
• Created: 11/Nov/14 18:47
• Updated: 25/Oct/15 16:52
• Resolved: 13/Feb/15 20:22

Description

The check_user function in container-executor.c can cause a segmentation fault if banned.users is not provided but the user is detected as one of the default users. In that scenario it will call free_values on a NULL pointer.

Issue Links

• duplicates: YARN-1681 When "banned.users" is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
• is duplicated by: YARN-3180 container-executor gets SEGV for default banned user
• is duplicated by: YARN-2898 Contaniner-executor prints out wrong error information when failed