Integrated: 8263742: (bf) MappedByteBuffer.force() should use the capacity as its upper bound

[Brian Burkhalter]

On Wed, 17 Mar 2021 16:49:27 GMT, Brian Burkhalter <bpb at openjdk.org> wrote:

> Prior to JDK 15, the method `java.nio.MappedByteBuffer.force()` wrote back the entire contents of the buffer, i.e., the half-open range `[0,capacity())`. In JDK 15 the upper bound of the write-back changed from `capacity()` to `limit()`. The change was inadvertent through a chain of fixes outlined in the description of the associated issue. This request is to change back to the previous behavior and use the capacity instead of the limit as the upper bound of the write-back.

This pull request has now been integrated.

Changeset: fa0f1614
Author:    Brian Burkhalter <bpb at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/fa0f1614
Stats:     8 lines in 1 file changed: 0 ins; 0 del; 8 mod

8263742: (bf) MappedByteBuffer.force() should use the capacity as its upper bound

Reviewed-by: adinn, alanb

-------------

PR: https://git.openjdk.java.net/jdk/pull/3052