hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2847) Linux native container executor segfaults if default banned user detected
Date Tue, 25 Nov 2014 08:50:13 GMT

    [ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224245#comment-14224245
] 

zhihai xu commented on YARN-2847:
---------------------------------

Will the second solution(set it to DEFAULT_BANNED_USERS if get_values returns NULL) be better?
With second solution, we needn't check null and we only need check DEFAULT_BANNED_USERS before
calling free_values.

> Linux native container executor segfaults if default banned user detected
> -------------------------------------------------------------------------
>
>                 Key: YARN-2847
>                 URL: https://issues.apache.org/jira/browse/YARN-2847
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.5.0
>            Reporter: Jason Lowe
>            Assignee: chang li
>         Attachments: yarn2847notest.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message