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

Hadoop QA commented on YARN-2847:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12698521/YARN-2487.05.trunk.patch
  against trunk revision 58cb9f5.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:red}-1 eclipse:eclipse{color}.  The patch failed to build with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6623//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6623//console

This message is automatically generated.

> 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, 2.4.1, 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Chang Li
>         Attachments: YARN-2487.04.trunk.patch, YARN-2487.05.trunk.patch, 
> 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)

Reply via email to