| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8348767 | 21.0.8-oracle | Johny Jose | P4 | Open | Unresolved | |
| JDK-8348768 | 17.0.16-oracle | Johny Jose | P4 | Open | Unresolved | |
| JDK-8348769 | 11.0.28-oracle | Johny Jose | P4 | Open | Unresolved | |
| JDK-8348770 | 8u461 | Johny Jose | P4 | Open | Unresolved |
Class j.m.BigInteger exposes some constructors accepting byte array arguments. According to the specification, they assume that the arrays are not racily modified by other threads during construction. If that happens anyway, there's no guarantee about the externally visible value of the new instance.
This change proposes to enhance the robustness of these constructors in the presence of racy modifications by improving guarantees on internal invariants. Like the current code, however, it ensures predictable outcomes to the caller only if the array is not modified during construction.
This change proposes to enhance the robustness of these constructors in the presence of racy modifications by improving guarantees on internal invariants. Like the current code, however, it ensures predictable outcomes to the caller only if the array is not modified during construction.
- backported by
-
JDK-8348767 Enhance robustness of some j.m.BigInteger constructors
-
- Open
-
-
-
- Open
-
-
-
- Open
-
-
-
- Open
-
- csr for
-
JDK-8319327 Enhance robustness of some j.m.BigInteger constructors
-
- Closed
-
(2 links to)