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 "Peter Bacsko (Jira)" <ji...@apache.org> on 2019/12/12 10:51:00 UTC
[jira] [Comment Edited] (YARN-10018) container-executor: possible
-1 return value of fork() is not always checked
[ https://issues.apache.org/jira/browse/YARN-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994496#comment-16994496 ]
Peter Bacsko edited comment on YARN-10018 at 12/12/19 10:50 AM:
----------------------------------------------------------------
[~szegedim], [~eyang], [~ebadger] do you have some time to check this out? Priority is not critical.
was (Author: pbacsko):
[~szegedim], [~eyang] do you have some time to check this out? Priority is not critical.
> container-executor: possible -1 return value of fork() is not always checked
> ----------------------------------------------------------------------------
>
> Key: YARN-10018
> URL: https://issues.apache.org/jira/browse/YARN-10018
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Attachments: YARN-10018-001.patch, YARN-10018-001.patch
>
>
> There are some places in the container-executor native, where the {{fork()}} call is not handled properly. This operation can fail with -1, but sometimes the necessary if branch is missing to validate that it's been successful.
> Also, at one location, the return value is defined as an {{int}}, not {{pid_t}}. It's better to handle this transparently and change it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org