-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8293842: IPv6-only systems throws UnsupportedOperationException for several socket/TCP options #10278
Conversation
…everal socket/TCP options
👋 Welcome back manc! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the indentation, LGTM. Thanks!
The proposed changes look reasonable. I have imported the PR and run tier2 test and observed no regressions. |
@caoman This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 13 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thank you all for the quick review and feedback! |
/contributor add martin Martin initially implemented this fix a while back. |
@caoman |
/integrate |
Going to push as commit 9a40b76.
Your commit was automatically rebased without conflicts. |
The changes that you integrated aren't the same as the changes that were reviewed. What you have is okay but if you make changes in response to reviewer feedback then you should really wait to see if there are comments on the changes. |
I see. Apology for that. I'll make sure to wait for approvals for the latest commit in the future. |
Hi all,
Could anyone review this bug fix for ipv6-only system? See https://bugs.openjdk.org/browse/JDK-8293842 for detailed description of this bug.
Ideally, the
socket(PF_INET6, ...)
orsocket(PF_INET, ...)
call should depend on the value ofipv6_available()
. However, this is only easy to do in net_util_md.c. Without checkingipv6_available()
in <Linux|MacOSX>SocketOptions.c, I'm not sure if it is possible for ipv6 and ipv4 sockets to differ in the options they support.For example, for a system with both ipv6 and ipv4, if ipv6 supports TCP_KEEPIDLE but ipv4 does not, then there might be a problem to always report TCP_KEEPIDLE as supported.
I noticed https://bugs.openjdk.org/browse/JDK-8290349 added "isIPv6" parameter to a few functions in <Linux|MacOSX>SocketOptions.c. However, it is not applicable to the
socketOptionSupported()
function. This change is more similar to theJava_jdk_net_MacOSXSocketOptions_ipDontFragmentSupported0()
function.-Man
Progress
Issue
Reviewers
Contributors
<martin@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10278/head:pull/10278
$ git checkout pull/10278
Update a local copy of the PR:
$ git checkout pull/10278
$ git pull https://git.openjdk.org/jdk pull/10278/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10278
View PR using the GUI difftool:
$ git pr show -t 10278
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10278.diff