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

Hadoop QA commented on HDFS-6439:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12649842/HDFS-6439.004.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

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

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

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-nfs hadoop-hdfs-project/hadoop-hdfs 
hadoop-hdfs-project/hadoop-hdfs-nfs:

                  org.apache.hadoop.fs.TestHdfsNativeCodeLoader

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

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

This message is automatically generated.

> NFS should not reject NFS requests to the NULL procedure whether port 
> monitoring is enabled or not
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-6439
>                 URL: https://issues.apache.org/jira/browse/HDFS-6439
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>    Affects Versions: 2.4.0
>            Reporter: Brandon Li
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-6439.003.patch, HDFS-6439.004.patch, 
> HDFS-6439.patch, HDFS-6439.patch, 
> linux-nfs-disallow-request-from-nonsecure-port.pcapng, 
> mount-nfs-requests.pcapng
>
>
> As discussed in HDFS-6406, this JIRA is to track the follow update:
> 1. Port monitoring is the feature name with traditional NFS server and we may 
> want to make the config property (along with related variable 
> allowInsecurePorts) something as dfs.nfs.port.monitoring. 
> 2 . According to RFC2623 (http://www.rfc-editor.org/rfc/rfc2623.txt):
> {quote}    Whether port monitoring is enabled or not, NFS servers SHOULD NOT 
> reject NFS requests to the NULL procedure (procedure number 0). See 
> subsection 2.3.1, "NULL procedure" for a complete explanation. {quote}
> I do notice that NFS clients (most time) send mount NULL and nfs NULL from 
> non-privileged port. If we deny NULL call in mountd or nfs server, the client 
> can't mount the export even as user root.
> 3. it would be nice to have the user guide updated for the port monitoring 
> feature.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to