And just to clarify, are you proposing that change only in the BSD port
repo or is that being considered for JDK mainline? I think it might be
OK to propose it to JDK mainline itself given the nature of the change.
Alan, Daniel or Michael, do you think it should be OK to do that in JDK
mainline?
-Jaikiran
On 05/10/26 7:16 pm, Jaikiran Pai wrote:
Hello Harald,
The change looks reasonable to me. Is this change prompted due to the
recent change integrated in JDK mainline for macos
https://github.com/openjdk/jdk/pull/32961. Or did something start
failing, independently, on some recent version of BSD too?
-Jaikiran
On 05/10/26 7:09 pm, Harald Eilertsen wrote:
Hi,
I am looking for someone to help review this trivial change to the
BSD port. We
want upstream reviewers so that it becomes easier when the time comes to
merge the port into the mainline in the future.
Thanks a lot in advance!
Harald Eilertsen
----- Forwarded message from Harald Eilertsen <[email protected]>
-----
Date: Thu, 1 Oct 2026 12:18:44 GMT
From: Harald Eilertsen <[email protected]>
To: [email protected]
Subject: [bsd-port:bsd-port] RFR: Clamp SO_LINGER to valid range on BSD
The BSDs store the `SO_LINGER` value in a signed short internally, so
we need to clamp the value to 32767 on those systems. This also
updates the SetSoLinger test case for BSD systems.
This work is sponsored by The FreeBSD Foundation
---------
- [x] I confirm that I make this contribution in accordance with the
[OpenJDK Interim AI Policy](https://openjdk.org/legal/ai).
-------------
Commit messages:
- Reduce max SO_LINGER value for BSD
- Fix SetSoLinger.java test case
Changes: https://git.openjdk.org/bsd-port/pull/16/files
Webrev: https://webrevs.openjdk.org/?repo=bsd-port&pr=16&range=00
Stats: 7 lines in 2 files changed: 2 ins; 0 del; 5 mod
Patch: https://git.openjdk.org/bsd-port/pull/16.diff
Fetch: git fetch https://git.openjdk.org/bsd-port.git
pull/16/head:pull/16
PR: https://git.openjdk.org/bsd-port/pull/16
----- End forwarded message -----
