On Mon, 13 Mar 2023 15:27:30 GMT, Jaikiran Pai <j...@openjdk.org> wrote:
>> Can I please get a review for this change which proposes to fix the issue >> reported in https://bugs.openjdk.org/browse/JDK-8206890? >> >> The `jlink` command allows a `--endian` option to specify the byte order in >> the generated image. Before this change, when such a image was being >> launched, the code would assume the byte order in the image to be the native >> order of the host where the image is being launched. That would result in >> failure to launch java, as noted in the linked issue. >> >> The commit in this PR, changes relevant places to not assume native order >> and instead determine the byte order by reading the magic bytes in the image >> file's header content. >> >> A new jtreg test has been added which reproduces the issue and verifies the >> fix. > > Jaikiran Pai has updated the pull request incrementally with one additional > commit since the last revision: > > no need for security manager checks in jlink src/jdk.jlink/share/classes/jdk/tools/jlink/internal/JlinkTask.java line 889: > 887: // the "java.base" module file used to create the image > 888: return Files.isSameFile(javaBasePath, > 889: > currentPlatformJmods.resolve(Path.of("java.base.jmod"))); You can reduce this to resolve("java.base.jmod"). ------------- PR: https://git.openjdk.org/jdk/pull/11943
