[HADOOP-11674] oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.1, 2.7.0, 3.0.0-alpha1
• Component/s: io
• Labels: 2.6.1-candidate
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Sean Busbey
• Reporter: Sean Busbey
• Created: 05/Mar/15 05:15
• Updated: 30/Aug/16 01:30
• Resolved: 05/Mar/15 07:39

Description

A common optimization in the io classes for Input/Output Streams is to save a single length-1 byte array to use in single byte read/write calls.

CryptoInputStream and CryptoOutputStream both attempt to follow this practice but mistakenly mark the array as static. That means that only a single instance of each can be present in a JVM safely.