[
https://issues.apache.org/jira/browse/HADOOP-11040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138938#comment-14138938
]
Hudson commented on HADOOP-11040:
---------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1900 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1900/])
HADOOP-11040. Return value of read(ByteBuffer buf) in CryptoInputStream is
incorrect in some cases. (Yi Liu via wang) (wang: rev
47e5e19831a363aa4d675fd23ab0d06e86809094)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/crypto/CryptoStreamsTestBase.java
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/CryptoInputStream.java
> Return value of read(ByteBuffer buf) in CryptoInputStream is incorrect in
> some cases
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-11040
> URL: https://issues.apache.org/jira/browse/HADOOP-11040
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.6.0
> Reporter: Yi Liu
> Assignee: Yi Liu
> Fix For: 2.6.0
>
> Attachments: HADOOP-11040.001.patch
>
>
> In {{CryptoInputStream}}, for {{int read(ByteBuffer buf))}}, if there is
> unread value in outBuffer, then the current return value is incorrect. This
> case happens when caller uses bytes array read firstly and then do the
> ByteBuffer read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
