[
https://issues.apache.org/jira/browse/HADOOP-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303322#comment-14303322
]
Hudson commented on HADOOP-11494:
---------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #90 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/90/])
HADOOP-11494. Lock acquisition on WrappedInputStream#unwrappedRpcBuffer may
race with another thread. Contributed by Ted Yu. (benoy: rev
3472e3bd6c50558870b86c9ccfea5072385fa991)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/SaslRpcClient.java
> Lock acquisition on WrappedInputStream#unwrappedRpcBuffer may race with
> another thread
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-11494
> URL: https://issues.apache.org/jira/browse/HADOOP-11494
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: hadoop-11494-001.patch, hadoop-11494-002.patch
>
>
> In SaslRpcClient, starting at line 576:
> {code}
> public int read(byte[] buf, int off, int len) throws IOException {
> synchronized(unwrappedRpcBuffer) {
> // fill the buffer with the next RPC message
> if (unwrappedRpcBuffer.remaining() == 0) {
> readNextRpcPacket();
> }
> {code}
> readNextRpcPacket() may assign another ByteBuffer to unwrappedRpcBuffer,
> making the lock on previous ByteBuffer not useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
