JDK-8168127 : FilePermissionCollection merges incorrectly
- Type: Bug
- Component: core-libs
- Sub-Component: java.io
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-10-18
- Updated: 2016-11-26
- Resolved: 2016-10-31
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b143Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
When a FilePermission is added into a FilePermissionCollection, it might be merged into an existing FilePermission which has the same name. The JavaIOFilePermissionAccess::newPermUsingAltPath method might create a new FilePermission with the same name but different internals. If it is merged with a "normal" FilePermission with the name, the merge will go wrong.