hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5195) Prevent passing null pointer to mlock and munlock.
Date Fri, 13 Sep 2013 20:25:52 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-5195:
--------------------------------

    Attachment: HDFS-5195.2.patch

bq. Let's add the check after mlock or munlock fails.

Sounds good.  Here is a new patch.
                
> Prevent passing null pointer to mlock and munlock.
> --------------------------------------------------
>
>                 Key: HDFS-5195
>                 URL: https://issues.apache.org/jira/browse/HDFS-5195
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: HDFS-4949
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-5195.1.patch, HDFS-5195.2.patch
>
>
> According to JNI documentation, it is optional for the JVM to support the {{GetDirectBufferAddress}}
function.  If unsupported, then the function will return null.  This is probably a very rare
thing, but let's be defensive by checking the return value for null and throwing an exception
instead of passing null down to {{mlock}} and {{munlock}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message