Re: RFR: 8353197: Document preconditions for JavaLangAccess methods [v4]

2025-05-12 Thread Jaikiran Pai
On Fri, 9 May 2025 08:31:35 GMT, Volkan Yazici wrote: >> Document preconditions on certain `JavaLangAccess` methods that use >> operations either unsafe and/or without range checks. > > Volkan Yazici has updated the pull request incrementally with one additional > commit since the last revision

Re: RFR: 8353197: Document preconditions for JavaLangAccess methods [v4]

2025-05-12 Thread Jaikiran Pai
On Fri, 9 May 2025 08:31:35 GMT, Volkan Yazici wrote: >> Document preconditions on certain `JavaLangAccess` methods that use >> operations either unsafe and/or without range checks. > > Volkan Yazici has updated the pull request incrementally with one additional > commit since the last revision

Re: RFR: 8353197: Document preconditions for JavaLangAccess methods [v2]

2025-05-07 Thread Jaikiran Pai
On Wed, 7 May 2025 07:29:55 GMT, Volkan Yazici wrote: >> Document preconditions on certain `JavaLangAccess` methods that use >> operations either unsafe and/or without range checks. > > Volkan Yazici has updated the pull request incrementally with one additional > commit since the last revision

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API [v2]

2025-04-24 Thread Jaikiran Pai
On Wed, 23 Apr 2025 07:54:39 GMT, Jaikiran Pai wrote: >> src/java.base/share/classes/sun/security/ssl/X509KeyManagerImpl.java line >> 366: >> >>> 364: } >>> 365: >>> 366: public String chooseServerAlias(String keyType, >> >>

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-23 Thread Jaikiran Pai
On Tue, 22 Apr 2025 18:55:28 GMT, Artur Barashev wrote: >> Hi, >> >> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for >> the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). >> >> The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Cli

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-23 Thread Jaikiran Pai
On Tue, 22 Apr 2025 19:11:24 GMT, Artur Barashev wrote: >> test/jdk/java/net/httpclient/http3/H3QuicTLSConnection.java line 96: >> >>> 94: //System.setProperty("javax.net.ssl.trustStore", KEYSTORE); >>> 95: //System.setProperty("javax.net.ssl.trustStorePassword", >>> PASSWORD);

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-23 Thread Jaikiran Pai
On Tue, 22 Apr 2025 18:56:19 GMT, Artur Barashev wrote: >> Hi, >> >> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for >> the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). >> >> The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Cli

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-23 Thread Jaikiran Pai
On Tue, 22 Apr 2025 16:10:19 GMT, Artur Barashev wrote: >> Hi, >> >> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for >> the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). >> >> The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Cli

Re: Integrated: Merge ed30fce6df57b1cbf7a6efebabc3558550f8ec16

2025-04-16 Thread Jaikiran Pai
On Wed, 16 Apr 2025 11:20:36 GMT, Jaikiran Pai wrote: > This brings in the CPU25_04 changes into the master branch. Thank you Daniel for the review. - PR Comment: https://git.openjdk.org/jdk/pull/24683#issuecomment-2809280611

Integrated: Merge ed30fce6df57b1cbf7a6efebabc3558550f8ec16

2025-04-16 Thread Jaikiran Pai
On Wed, 16 Apr 2025 11:20:36 GMT, Jaikiran Pai wrote: > This brings in the CPU25_04 changes into the master branch. This pull request has now been integrated. Changeset: c6243fc2 Author: Jaikiran Pai URL: https://git.openjdk.org/jdk/commit/c6243fc27fafb1ff89f8610ead3acd87030ca

Integrated: Merge ed30fce6df57b1cbf7a6efebabc3558550f8ec16

2025-04-16 Thread Jaikiran Pai
This brings in the CPU25_04 changes into the master branch. - Commit messages: The merge commit only contains trivial merges, so no merge-specific webrevs have been generated. Changes: https://git.openjdk.org/jdk/pull/24683/files Stats: 0 lines in 0 files changed: 0 ins; 0 del;

Integrated: 8353787: Increased number of SHA-384-Digest java.util.jar.Attributes$Name instances leading to higher memory footprint

2025-04-07 Thread Jaikiran Pai
On Mon, 7 Apr 2025 06:34:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which proposes to address the > increase in memory footprint of an application that uses signed JAR files, > signed with `SHA-384` digest algorithm? This addresses > https://bugs.openjd

Re: RFR: 8353787: Increased number of SHA-384-Digest java.util.jar.Attributes$Name instances leading to higher memory footprint

2025-04-07 Thread Jaikiran Pai
On Mon, 7 Apr 2025 06:34:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which proposes to address the > increase in memory footprint of an application that uses signed JAR files, > signed with `SHA-384` digest algorithm? This addresses > https://bugs.openjd

Re: RFR: 8353787: Increased number of SHA-384-Digest java.util.jar.Attributes$Name instances leading to higher memory footprint

2025-04-07 Thread Jaikiran Pai
On Mon, 7 Apr 2025 12:49:45 GMT, Sean Mullan wrote: > I suggest making this a P3 since it sounds like it would be useful to > backport to 21. Done - I've marked it as a P3, and I agree that this is worth backporting. - PR Comment: https://git.openjdk.org/jdk/pull/24475#issuecommen

Re: RFR: 8353787: Increased number of SHA-384-Digest java.util.jar.Attributes$Name instances leading to higher memory footprint

2025-04-06 Thread Jaikiran Pai
On Mon, 7 Apr 2025 06:34:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which proposes to address the > increase in memory footprint of an application that uses signed JAR files, > signed with `SHA-384` digest algorithm? This addresses > https://bugs.openjd

RFR: 8353787: Increased number of SHA-384-Digest java.util.jar.Attributes instances leading to higher memory footprint

2025-04-06 Thread Jaikiran Pai
Can I please get a review of this change which proposes to address the increase in memory footprint of an application that uses signed JAR files, signed with `SHA-384` digest algorithm? This addresses https://bugs.openjdk.org/browse/JDK-8353787. As noted in that issue and the linked mailing lis

Re: RFR: 8349348: Refactor ClassLoaderDeadlock.sh and Deadlock.sh to run fully in java [v3]

2025-03-11 Thread Jaikiran Pai
On Thu, 6 Mar 2025 11:49:12 GMT, Mikhail Yankelevich wrote: >> Refactor the following to run fully in java: >> test/java/security//Security/ClassLoaderDeadlock/ClassLoaderDeadlock.sh >> test/java/security//Security/ClassLoaderDeadlock/Deadlock.sh > > Mikhail Yankelevich has updated the pull requ

Re: RFR: 8349348: Refactor ClassLoaderDeadlock.sh and Deadlock.sh to run fully in java [v2]

2025-03-06 Thread Jaikiran Pai
On Thu, 27 Feb 2025 17:49:48 GMT, Mikhail Yankelevich wrote: >> Refactor the following to run fully in java: >> test/java/security//Security/ClassLoaderDeadlock/ClassLoaderDeadlock.sh >> test/java/security//Security/ClassLoaderDeadlock/Deadlock.sh > > Mikhail Yankelevich has updated the pull req

Re: RFR: 8349348: Refactor ClassLoaderDeadlock.sh and Deadlock.sh to run fully in java

2025-02-28 Thread Jaikiran Pai
On Thu, 27 Feb 2025 16:08:09 GMT, Jaikiran Pai wrote: > Hello Mikhail, since we are updating these tests to move away from the shell > tests, could you also see if the deadlock.jar file which has been committed > into the repo, can be generated dynamically within the test itself. I

Re: RFR: 8349348: Refactor ClassLoaderDeadlock.sh and Deadlock.sh to run fully in java

2025-02-27 Thread Jaikiran Pai
On Tue, 4 Feb 2025 14:08:05 GMT, Mikhail Yankelevich wrote: > Refactor the following to run fully in java: > test/java/security//Security/ClassLoaderDeadlock/ClassLoaderDeadlock.sh > test/java/security//Security/ClassLoaderDeadlock/Deadlock.sh Hello Mikhail, since we are updating these tests to

Re: RFR: 8350476: Fix typo introduced in JDK-8350147

2025-02-21 Thread Jaikiran Pai
On Sat, 22 Feb 2025 02:25:42 GMT, Bradford Wetmore wrote: > Typo: s/ficticious/fictitious/ > > No unit test. Check that javadoc still builds. Marked as reviewed by jpai (Reviewer). - PR Review: https://git.openjdk.org/jdk/pull/23733#pullrequestreview-2634730559

Re: RFR: 8347946: Add API note that caller should validate/trust signers to the getCertificates and getCodeSigners methods of JarEntry and JarURLConnection

2025-02-19 Thread Jaikiran Pai
On Wed, 19 Feb 2025 10:43:06 GMT, Marcono1234 wrote: >> This change adds an API note to these methods recommending that the caller >> should perform further validation steps on the code signers that signed the >> JAR file, such as validating the code signer's certificate chain, and >> determin

Re: RFR: 8347946: Add API note that caller should validate/trust signers to the getCertificates and getCodeSigners methods of JarEntry and JarURLConnection

2025-02-15 Thread Jaikiran Pai
On Thu, 13 Feb 2025 16:27:03 GMT, Sean Mullan wrote: > This change adds an API note to these methods recommending that the caller > should perform further validation steps on the code signers that signed the > JAR file, such as validating the code signer's certificate chain, and > determining

Re: RFR: 8347946: Add API note that caller should validate/trust signers to the getCertificates and getCodeSigners methods of JarEntry and JarURLConnection

2025-02-13 Thread Jaikiran Pai
On Thu, 13 Feb 2025 16:27:03 GMT, Sean Mullan wrote: > This change adds an API note to these methods recommending that the caller > should perform further validation steps on the code signers that signed the > JAR file, such as validating the code signer's certificate chain, and > determining

Re: RFR: 8347597: HttpClient: improve exception reporting when closing connection [v2]

2025-01-14 Thread Jaikiran Pai
On Tue, 14 Jan 2025 20:29:38 GMT, Daniel Fuchs wrote: >> There are a few places in the HttpClient code base where we close the >> connection when some error/exception happens. This can some time trigger a >> race condition where closing the connection in turns causes a "connection >> closed lo

Re: RFR: 8347597: HttpClient: improve exception reporting when closing connection

2025-01-14 Thread Jaikiran Pai
On Mon, 13 Jan 2025 16:07:45 GMT, Daniel Fuchs wrote: > There are a few places in the HttpClient code base where we close the > connection when some error/exception happens. This can some time trigger a > race condition where closing the connection in turns causes a "connection > closed locall

Re: RFR: 8347597: HttpClient: improve exception reporting when closing connection

2025-01-14 Thread Jaikiran Pai
On Mon, 13 Jan 2025 16:07:45 GMT, Daniel Fuchs wrote: > There are a few places in the HttpClient code base where we close the > connection when some error/exception happens. This can some time trigger a > race condition where closing the connection in turns causes a "connection > closed locall

Re: RFR: 8346468: SM cleanup of common test library [v4]

2025-01-10 Thread Jaikiran Pai
On Fri, 10 Jan 2025 17:10:03 GMT, Roger Riggs wrote: >> SM Cleanup of common test library test/lib/...: >> >> Remove unnecessary catches of SecurityException >> Remove AccessController and doPrivileged from SimpleSSLContext and >> ProcessTools. > > Roger Riggs has updated the pull request incre

Re: RFR: 8346468: SM cleanup of common test library [v3]

2025-01-10 Thread Jaikiran Pai
On Wed, 18 Dec 2024 21:07:14 GMT, Roger Riggs wrote: >> SM Cleanup of common test library test/lib/...: >> >> Remove unnecessary catches of SecurityException >> Remove AccessController and doPrivileged from SimpleSSLContext and >> ProcessTools. > > Roger Riggs has updated the pull request incre

Re: RFR: 8346468: SM cleanup of common test library [v3]

2025-01-10 Thread Jaikiran Pai
On Wed, 18 Dec 2024 21:07:14 GMT, Roger Riggs wrote: >> SM Cleanup of common test library test/lib/...: >> >> Remove unnecessary catches of SecurityException >> Remove AccessController and doPrivileged from SimpleSSLContext and >> ProcessTools. > > Roger Riggs has updated the pull request incre

Integrated: 8345286: Remove use of SecurityManager API from misc areas

2024-12-04 Thread Jaikiran Pai
On Mon, 2 Dec 2024 12:13:57 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes usages of > SecurityManager related APIs and some leftover related to SecurityManager > changes? > > This addresses https://bugs.openjdk.org/browse/JDK-8345286

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9]

2024-12-04 Thread Jaikiran Pai
On Tue, 3 Dec 2024 06:12:13 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which removes usages of >> SecurityManager related APIs and some leftover related to SecurityManager >> changes? >> >> This addresses https://bugs.openjdk.org/bro

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9]

2024-12-03 Thread Jaikiran Pai
On Tue, 3 Dec 2024 06:12:13 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which removes usages of >> SecurityManager related APIs and some leftover related to SecurityManager >> changes? >> >> This addresses https://bugs.openjdk.org/bro

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 17:47:57 GMT, Daniel Fuchs wrote: >> Jaikiran Pai has updated the pull request with a new target base due to a >> merge or a rebase. The pull request now contains 13 commits: >> >> - merge latest from master branch >> - remove changes to >

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 18:54:33 GMT, Alan Bateman wrote: >> src/java.base/share/classes/jdk/internal/misc/InnocuousThread.java line 31: >> >>> 29: >>> 30: /** >>> 31: * A thread that has no permissions, is not a member of any user-defined >> >> I think you can also remove the words "has no permis

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: - merge latest from master branch - remove permission text from InnocuousThread - merge latest from master branch

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v5]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision: Update src/java.base/linux/classes/jdk/internal/platform/CgroupSubsystemController.java Co-authored-by: Severin Gehwolf --

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v7]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 15:42:37 GMT, Alan Bateman wrote: >> Jaikiran Pai has updated the pull request incrementally with one additional >> commit since the last revision: >> >> remove changes to >> src/java.base/unix/classes/sun/security/provider/NativePRNG.java

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 13:43:41 GMT, Severin Gehwolf wrote: >> Jaikiran Pai has updated the pull request incrementally with four additional >> commits since the last revision: >> >> - remove unnecessary space >> - Path.of() instead of Paths.get() >> - fix

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 13 commits: - merge latest from master branch - remove changes to src/java.base/unix/classes/sun/security/provider/NativePRNG.jav

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v3]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision: Path.of() instead of Paths.get() in CgroupV2Subsystem.java - Changes: - all: https://git.openjdk.org/jdk/pull/22478/files - n

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 14:25:12 GMT, Alan Bateman wrote: >> Jaikiran Pai has updated the pull request incrementally with two additional >> commits since the last revision: >> >> - remove unused import >> - replace remaining Paths.get() with Path.of() in the updated

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v7]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision: remove changes to src/java.base/unix/classes/sun/security/provider/NativePRNG.java - Changes: - all: https://git.openjdk.org

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v5]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 14:17:10 GMT, Severin Gehwolf wrote: > cgroups changes look good. Haven't looked at the other bits. Thank you Severin. > src/java.base/linux/classes/jdk/internal/platform/CgroupSubsystemController.java > line 29: > >> 27: package jdk.internal.platform; >> 28: >> 29: import

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 14:07:45 GMT, Severin Gehwolf wrote: >> Is the catch for `UncheckedIOException` due to some previously known failure >> resulting in the use of these APIs? > > Without using `Files.lines()` no `UncheckedIOException` would be thrown. Just > `IOException` and `null` returned. T

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with two additional commits since the last revision: - remove unused import - replace remaining Paths.get() with Path.of() in the updated files - Changes: - all: https://git.open

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v4]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision: Update src/java.base/linux/classes/jdk/internal/platform/cgroupv2/CgroupV2Subsystem.java Co-authored-by: Severin Gehwolf --

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v3]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 13:06:05 GMT, Severin Gehwolf wrote: >> Jaikiran Pai has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Path.of() instead of Paths.get() in CgroupV2Subsystem.java > > src/java.base/linux

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2]

2024-12-02 Thread Jaikiran Pai
ced and tier testing is currently in progress. Jaikiran Pai has updated the pull request incrementally with four additional commits since the last revision: - remove unnecessary space - Path.of() instead of Paths.get() - fix formatting of try-with-resources in CgroupSubsystemController.java - le

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2]

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 12:42:47 GMT, Alan Bateman wrote: >> Jaikiran Pai has updated the pull request incrementally with four additional >> commits since the last revision: >> >> - remove unnecessary space >> - Path.of() instead of Paths.get() >> - fix

RFR: 8345286: Remove use of SecurityManager API from misc areas

2024-12-02 Thread Jaikiran Pai
Can I please get a review of this change which removes usages of SecurityManager related APIs and some leftover related to SecurityManager changes? This addresses https://bugs.openjdk.org/browse/JDK-8345286. Most of these changes are trivial. The `src/java.base/linux/classes/jdk/internal/platf

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas

2024-12-02 Thread Jaikiran Pai
On Mon, 2 Dec 2024 12:13:57 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes usages of > SecurityManager related APIs and some leftover related to SecurityManager > changes? > > This addresses https://bugs.openjdk.org/browse/JDK-8345286

Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration [v2]

2024-11-26 Thread Jaikiran Pai
On Mon, 25 Nov 2024 20:06:33 GMT, Volkan Yazıcı wrote: >> Addresses [8344222](https://bugs.openjdk.org/browse/JDK-8344222) and removes >> `SecurityManager` and `doPrivileged()` usages from `Http(s)URLConnection` >> and `HttpConnectSocketImpl`. `tier2` and `tier3` results are on their way. > > V

Re: RFR: 8344310: Remove Security Manager dependencies from javax.crypto and com.sun.crypto packages [v2]

2024-11-18 Thread Jaikiran Pai
On Mon, 18 Nov 2024 13:11:26 GMT, Sean Mullan wrote: >> Now that JEP 486 is integrated, javax.crypto and com.sun.crypto >> implementation dependencies on System.getSecurityManager and >> AccessController.doPrivileged can be removed. > > Sean Mullan has updated the pull request incrementally wit

Re: RFR: 8344310: Remove Security Manager dependencies from javax.crypto and com.sun.crypto packages

2024-11-16 Thread Jaikiran Pai
On Fri, 15 Nov 2024 20:48:42 GMT, Sean Mullan wrote: > Now that JEP 486 is integrated, javax.crypto and com.sun.crypto > implementation dependencies on System.getSecurityManager and > AccessController.doPrivileged can be removed. Hello Sean, at the class declaration of `JceSecurity` in the `s

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2]

2024-11-16 Thread Jaikiran Pai
On Sat, 16 Nov 2024 01:59:43 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which removes calls to >> `SecurityManager` and `AccessController.doPrivileged()` from the >> `ProxySelector` and `DefaultProxySelector` classes? >> >> Apart from

Integrated: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-16 Thread Jaikiran Pai
On Fri, 15 Nov 2024 10:31:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes calls to > `SecurityManager` and `AccessController.doPrivileged()` from the > `ProxySelector` and `DefaultProxySelector` classes? > > Apart from the trivial removing

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 10:31:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes calls to > `SecurityManager` and `AccessController.doPrivileged()` from the > `ProxySelector` and `DefaultProxySelector` classes? > > Apart from the trivial removing

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2]

2024-11-15 Thread Jaikiran Pai
us > `doPriveleged()` call block. > > No new tests have been introduced. Existing tests in tier1 and tier2 continue > to pass with this change. Jaikiran Pai has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits:

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 10:31:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes calls to > `SecurityManager` and `AccessController.doPrivileged()` from the > `ProxySelector` and `DefaultProxySelector` classes? > > Apart from the trivial removing

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v4]

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 14:07:10 GMT, Daniel Fuchs wrote: >> Please find here a patch that cleans up the java.net.http module code to >> remove permission checks and doPriviliged calls. >> This was mostly mechanical. > > Daniel Fuchs has updated the pull request incrementally with one additional >

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v3]

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 10:25:18 GMT, Daniel Fuchs wrote: >> Please find here a patch that cleans up the java.net.http module code to >> remove permission checks and doPriviliged calls. >> This was mostly mechanical. > > Daniel Fuchs has updated the pull request with a new target base due to a > me

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v3]

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 10:25:18 GMT, Daniel Fuchs wrote: >> Please find here a patch that cleans up the java.net.http module code to >> remove permission checks and doPriviliged calls. >> This was mostly mechanical. > > Daniel Fuchs has updated the pull request with a new target base due to a > me

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-15 Thread Jaikiran Pai
On Fri, 15 Nov 2024 11:26:50 GMT, Daniel Fuchs wrote: > No CSR needed for removing those permissions. There's no visible change to > the public APIs, and no behavior change that was not already covered by JEP > 486 CSR, since permissions checks have now become deadcode. Or am I missing > somet

RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-15 Thread Jaikiran Pai
Can I please get a review of this change which removes calls to `SecurityManager` and `AccessController.doPrivileged()` from the `ProxySelector` and `DefaultProxySelector` classes? Apart from the trivial removing of those calls, the commit in this PR also removes the `getProxySelector` and `set

Re: RFR: 8344179: SecurityManager cleanup in the ZIP and JAR areas [v2]

2024-11-14 Thread Jaikiran Pai
On Thu, 14 Nov 2024 13:21:33 GMT, Eirik Bjørsnøs wrote: >> Please review this PR which cleans up security manager related code in >> `java.util.zip` and `java.util.jar`: >> >> * `JarFile` and `ZipFile` are updated to use `System::getProperty` instead >> of `GetPropertyAction::privilegedGetProp

Re: RFR: 8343925: [BACKOUT] JDK-8342650 Move getChars to DecimalDigits

2024-11-11 Thread Jaikiran Pai
On Mon, 11 Nov 2024 12:34:44 GMT, Shaojin Wen wrote: > 8343925 Feedback PR #21593 test/jdk/java/util/BitSet/HugeToString.java crash, > > I can't reproduce the problem on a MacBook M1 Max, but I agree that more > testing is needed, so let's roll it back first. I have verified that this backout

Re: RFR: 8342040: Further improve entry lookup performance for multi-release JARs [v3]

2024-10-30 Thread Jaikiran Pai
On Wed, 30 Oct 2024 16:17:20 GMT, Claes Redestad wrote: >> src/java.base/share/classes/java/util/zip/ZipFile.java line 1798: >> >>> 1796: >>> metaVersions.computeIfAbsent(hashCode, _ -> new BitSet()).set(version); >>> 1797: } catch (Ex

Re: RFR: 8342040: Further improve entry lookup performance for multi-release JARs [v3]

2024-10-30 Thread Jaikiran Pai
On Fri, 18 Oct 2024 13:59:32 GMT, Eirik Bjørsnøs wrote: >> Please review this PR which speeds up `JarFile::getEntry` lookup >> significantly for multi-release JAR files. >> >> The changes in this PR are motivated by the following insights: >> >> * `META-INF/versions/` is sparsely populated. >>

Integrated: Merge 490d099e234f27adef7d691d3c5a08ebdb550c5d

2024-10-16 Thread Jaikiran Pai
On Wed, 16 Oct 2024 10:31:12 GMT, Jaikiran Pai wrote: > This brings in CPU24_10 changes into master branch. This pull request has now been integrated. Changeset: cf5bb127 Author: Jaikiran Pai URL: https://git.openjdk.org/jdk/commit/cf5bb12731b0eefe53b99281453e40493ddafbe4 St

Re: RFR: Merge 490d099e234f27adef7d691d3c5a08ebdb550c5d

2024-10-16 Thread Jaikiran Pai
On Wed, 16 Oct 2024 10:31:12 GMT, Jaikiran Pai wrote: > This brings in CPU24_10 changes into master branch. Thank you Alan and Daniel for the reviews. - PR Comment: https://git.openjdk.org/jdk/pull/21533#issuecomment-2416550126

Re: RFR: Merge 490d099e234f27adef7d691d3c5a08ebdb550c5d [v2]

2024-10-16 Thread Jaikiran Pai
> This brings in CPU24_10 changes into master branch. Jaikiran Pai has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. - Changes: - all: https://git.openjdk.org/

RFR: Merge 490d099e234f27adef7d691d3c5a08ebdb550c5d

2024-10-16 Thread Jaikiran Pai
This brings in CPU24_10 changes into master branch. - Commit messages: - 8335713: Enhance vectorization analysis - 8332644: Improve graph optimizations - 8331446: Improve deserialization support - 8307383: Enhance DTLS connections - 8311208: Improve CDS Support - 8328544: Improv

Re: RFR: 8342003: ProblemList sun/security/tools/keytool/GenKeyPairSigner.java

2024-10-11 Thread Jaikiran Pai
On Sat, 12 Oct 2024 01:59:29 GMT, Daniel D. Daugherty wrote: > A trivial fix to ProblemList sun/security/tools/keytool/GenKeyPairSigner.java. Looks OK to me. - Marked as reviewed by jpai (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/21481#pullrequestreview-2363716720

Re: RFR: 8340133: Investigate if the java launcher could give hints about JShell

2024-10-09 Thread Jaikiran Pai
On Tue, 8 Oct 2024 15:28:17 GMT, Jan Lahoda wrote: > Currently, running `java` without any parameters will lead to an output that > is a full `--help`, which is over 100 lines (on my computer at least), and it > feels overwhelming. And many people might actually want to run JShell/REPL, > not

Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]

2024-10-01 Thread Jaikiran Pai
On Tue, 1 Oct 2024 05:39:09 GMT, Eirik Bjørsnøs wrote: >> Please review this cleanup PR which updates code and tests in `java.base` to >> consistently use `jdk.internal.util.ArraySupport.SOFT_MAX_ARRAY_LENGTH` >> when referring to the JVM's maximum array size implementation limit. >> Currentl

Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]

2024-10-01 Thread Jaikiran Pai
On Tue, 1 Oct 2024 05:39:09 GMT, Eirik Bjørsnøs wrote: >> Please review this cleanup PR which updates code and tests in `java.base` to >> consistently use `jdk.internal.util.ArraySupport.SOFT_MAX_ARRAY_LENGTH` >> when referring to the JVM's maximum array size implementation limit. >> Currentl

Integrated: 8340537: Typo in javadoc of java.util.jar.JarFile

2024-09-20 Thread Jaikiran Pai
On Fri, 20 Sep 2024 12:30:00 GMT, Jaikiran Pai wrote: > Can I please get a review of this trivial typo fix in `JarFile` class' > javadoc? This pull request has now been integrated. Changeset: 90d3a64b Author: Jaikiran Pai URL: https://git.openjdk.org

Re: RFR: 8340537: Typo in javadoc of java.util.jar.JarFile

2024-09-20 Thread Jaikiran Pai
On Fri, 20 Sep 2024 12:30:00 GMT, Jaikiran Pai wrote: > Can I please get a review of this trivial typo fix in `JarFile` class' > javadoc? Thank you all for the reviews. - PR Comment: https://git.openjdk.org/jdk/pull/21108#issuecomment-2364052197

RFR: 8340537: Typo in javadoc of java.util.jar.JarFile

2024-09-20 Thread Jaikiran Pai
Can I please get a review of this trivial typo fix in `JarFile` class' javadoc? - Commit messages: - 8340537: Typo in javadoc of java.util.jar.JarFile Changes: https://git.openjdk.org/jdk/pull/21108/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=21108&range=00 Issue: htt

Integrated: 8339834: Replace usages of -mx and -ms in some tests

2024-09-11 Thread Jaikiran Pai
On Tue, 10 Sep 2024 09:46:14 GMT, Jaikiran Pai wrote: > Can I please get a review of this trivial change which replaces the usages of > `-mx` and `-ms` to `-Xmx` and `-Xms` in tests and in one code comment? > > As noted in https://bugs.openjdk.org/browse/JDK-8339834, these

Re: RFR: 8339834: Replace usages of -mx and -ms in some tests [v3]

2024-09-11 Thread Jaikiran Pai
On Wed, 11 Sep 2024 09:19:21 GMT, Jaikiran Pai wrote: >> Can I please get a review of this trivial change which replaces the usages >> of `-mx` and `-ms` to `-Xmx` and `-Xms` in tests and in one code comment? >> >> As noted in https://bugs.openjdk.org/browse/JDK-83

Re: RFR: 8339834: Replace usages of -mx and -ms in some tests [v2]

2024-09-11 Thread Jaikiran Pai
On Wed, 11 Sep 2024 09:03:58 GMT, Alexey Ivanov wrote: >> Jaikiran Pai has updated the pull request incrementally with one additional >> commit since the last revision: >> >> update JImageToolTest too > > test/jdk/java/beans/Introspector/Test5102804.java line

Re: RFR: 8339834: Replace usages of -mx and -ms in some tests [v3]

2024-09-11 Thread Jaikiran Pai
deprecated and removed as part of > https://bugs.openjdk.org/browse/JDK-8286851. > > There are some more tests remaining in client-libs area which too require a > similar change. I'll be creating a separate JBS issue and PR for that. Jaikiran Pai has updated the pull request i

Re: RFR: 8339834: Replace usages of -mx and -ms in some tests [v2]

2024-09-10 Thread Jaikiran Pai
deprecated and removed as part of > https://bugs.openjdk.org/browse/JDK-8286851. > > There are some more tests remaining in client-libs area which too require a > similar change. I'll be creating a separate JBS issue and PR for that. Jaikiran Pai has updated the pull request i

RFR: 8339834: Replace usages of -mx and -ms in some tests

2024-09-10 Thread Jaikiran Pai
Can I please get a review of this trivial change which replaces the usages of `-mx` and `-ms` to `-Xmx` and `-Xms` in tests and in one code comment? As noted in https://bugs.openjdk.org/browse/JDK-8339834, these options are outdated and support for them will soon be deprecated and removed as par

Re: RFR: 8339261: Logs truncated in test javax/net/ssl/DTLS/DTLSRehandshakeTest.java

2024-09-05 Thread Jaikiran Pai
On Tue, 3 Sep 2024 13:07:47 GMT, Fernando Guallini wrote: > The test javax/net/ssl/DTLS/DTLSRehandshakeTest.java runs multiple scenarios, > generating a large amount of logging as a result. Since Jtreg truncates the > output when it becomes too large, the logs are often not useful for debuggin

Re: RFR: 8336289: Obliterate most references to _snprintf in the Windows JDK [v5]

2024-08-26 Thread Jaikiran Pai
On Mon, 26 Aug 2024 12:24:30 GMT, Julian Waters wrote: > If no objections are raised by tomorrow morning I'll proceed with integration I've run this PR against latest mainline in our CI for tier1, tier2 and tier3 and there were no failures. So yes, I think you can go ahead with the integration

Re: RFR: 8336289: Obliterate most references to _snprintf in the Windows JDK [v5]

2024-08-23 Thread Jaikiran Pai
On Sat, 24 Aug 2024 05:12:42 GMT, Julian Waters wrote: >> snprintf has been available for all officially and unofficially supported >> compilers for Windows, Visual Studio since version 2015 and gcc since, well, >> forever. snprintf is conforming to C99 since the start when compiling using >>

Re: RFR: 8336289: Obliterate most references to _snprintf in the Windows JDK [v3]

2024-08-04 Thread Jaikiran Pai
On Tue, 16 Jul 2024 08:59:20 GMT, Julian Waters wrote: >> snprintf has been available for all officially and unofficially supported >> compilers for Windows, Visual Studio since version 2015 and gcc since, well, >> forever. snprintf is conforming to C99 since the start when compiling using >>

Re: RFR: 8333317: Test sun/security/pkcs11/sslecc/ClientJSSEServerJSSE.java failed with: Invalid ECDH ServerKeyExchange signature

2024-07-15 Thread Jaikiran Pai
On Mon, 24 Jun 2024 12:07:49 GMT, Matthew Donovan wrote: > In this PR, I updated the version of NSS to 3.101 and removed the test from > the ProblemList for all platforms but linux-ppc64le (that bug is still > outstanding.) > > I also updated the skipTest logic in TestDSAKeyLength.java. Prior

Re: [jdk23] RFR: 8324841: PKCS11 tests still skip execution

2024-07-15 Thread Jaikiran Pai
On Mon, 24 Jun 2024 12:31:20 GMT, Matthew Donovan wrote: > 8324841: PKCS11 tests still skip execution This is a clean backport of a test-only fix. Looks good to me for JDK 23. - Marked as reviewed by jpai (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/19857#pullrequestrev

Re: RFR: 8321274: Rename ZipEntry.extraAttributes to ZipEntry.externalFileAttributes [v5]

2024-07-02 Thread Jaikiran Pai
On Sat, 29 Jun 2024 18:24:46 GMT, Eirik Bjørsnøs wrote: >> Please consider this PR which suggests we rename `ZipEntry.extraAttributes` >> to `ZipEntry.externalFileAttributes`. >> >> This field was introduced in >> [JDK-8218021](https://bugs.openjdk.org/browse/JDK-8218021), originally under >>

Re: RFR: 8321274: Rename ZipEntry.extraAttributes to ZipEntry.externalFileAttributes [v5]

2024-06-29 Thread Jaikiran Pai
On Sat, 29 Jun 2024 18:24:46 GMT, Eirik Bjørsnøs wrote: >> Please consider this PR which suggests we rename `ZipEntry.extraAttributes` >> to `ZipEntry.externalFileAttributes`. >> >> This field was introduced in >> [JDK-8218021](https://bugs.openjdk.org/browse/JDK-8218021), originally under >>

Re: RFR: 8241550: [macOS] SSLSocketImpl/ReuseAddr.java failed due to "BindException: Address already in use" [v2]

2024-05-23 Thread Jaikiran Pai
On Thu, 23 May 2024 09:11:33 GMT, Daniel Fuchs wrote: >> This is one of these tests that is not really fixable if any other process >> that might open a socket runs concurrently with it on the same machine: >> nothing can guarantee that if you open a socket, close it, then open a new >> socket

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v8]

2024-05-18 Thread Jaikiran Pai
On Fri, 17 May 2024 13:38:25 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v6]

2024-05-16 Thread Jaikiran Pai
On Thu, 16 May 2024 11:47:13 GMT, Maurizio Cimadamore wrote: >> src/java.base/share/classes/sun/launcher/resources/launcher.properties line >> 72: >> >>> 70: \ by code in modules for which native access is not >>> explicitly enabled.\n\ >>> 71: \ is one of "

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v6]

2024-05-16 Thread Jaikiran Pai
On Wed, 15 May 2024 16:08:17 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v6]

2024-05-16 Thread Jaikiran Pai
On Wed, 15 May 2024 16:08:17 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8321274: Rename ZipEntry.extraAttributes to ZipEntry.externalFileAttributes [v4]

2024-05-09 Thread Jaikiran Pai
On Fri, 8 Mar 2024 09:34:05 GMT, Eirik Bjørsnøs wrote: >> Please consider this PR which suggests we rename `ZipEntry.extraAttributes` >> to `ZipEntry.externalFileAttributes`. >> >> This field was introduced in >> [JDK-8218021](https://bugs.openjdk.org/browse/JDK-8218021), originally under >>

  1   2   3   >