You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Wei Yan (JIRA)" <ji...@apache.org> on 2014/12/03 23:43:13 UTC

[jira] [Commented] (YARN-2847) Linux native container executor segfaults if default banned user detected

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

Wei Yan commented on YARN-2847:
-------------------------------

Thanks for the fix, [~lichangleo]. There are some unnecessary changes in the latest patch, the blanks.
And for the testcase, do we really need the testcase for this fix, given that the testcase requires mapred user.

> 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: yarn2847.patch, yarn2847.patch, 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)