-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8266320: (bf) ReadOnlyBufferException in heap buffer put(String,int,int) should not be conditional #3809
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
Conversation
…nt) should not be conditional
👋 Welcome back marschall! A progress list of the required criteria for merging this PR into |
@marschall The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
@@ -1003,6 +1003,9 @@ public class Basic$Type$ | |||
catchReadOnlyBuffer(b, () -> rb.put(new String(new char[rb.remaining() + 1]))); | |||
catchReadOnlyBuffer(b, () -> rb.append(new String(new char[rb.remaining() + 1]))); | |||
|
|||
// 8266320 |
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.
The bug ID should be deleted here and appended to the list of bug IDs in Basic.java.
The more recent copyright year needs to be 2021 in all files changed. |
@@ -285,6 +284,9 @@ class Heap$Type$Buffer$RW$ | |||
src.getChars(start, end, hb, ix(pos)); | |||
position(pos + length); | |||
return this; | |||
#else[rw] | |||
throw new ReadOnlyBufferException(); | |||
#end[rw] |
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.
I assume this isn't technically a bug in that it's unspecified which exception is thrown when the buffer is read-only and an index is out of range. The change is okay of course. It would be useful to run the tests without the addition to Basic-X.java.template as I would expect this case to be covered by an existing test already.
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.
would expect this case to be covered by an existing test already.
Upon closer inspection this line seems to cover it already. It also establishes the existing behavior to be throwing ReadOnlyBufferException
and not BufferOverflowException
. Should I undo the added test in Basic-X.java.template
and not add the bug id to Basic.java
?
catchReadOnlyBuffer(b, () -> rb.put(new String(new char[rb.remaining() + 1]))); |
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.
Yes, I expected it was tested already so I think you can drop the change to Basic-X.java.template from the patch.
That leaves the change to throw ReadOnlyBufferException unconditionally. As I said, if someone were to invoke this method on a read-only CharBuffer and with an out of range start or end index then ReadOnlyBufferException or IndexOutOfBoundsException are applicable. Existing behavior is to throw IOOBE. It's possible, but probably unlikely, that the behavior change will be observed by someone. A Release Note could be helpful.
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.
Probably order of checks with respect to read-only, IOOBEs, and over/underflow has changed in various places and needs to be reviewed.
@marschall 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 161 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@AlanBateman, @bplb) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@marschall |
/sponsor |
@bplb @marschall Since your change was applied there have been 161 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 45760d4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3809/head:pull/3809
$ git checkout pull/3809
Update a local copy of the PR:
$ git checkout pull/3809
$ git pull https://git.openjdk.java.net/jdk pull/3809/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3809
View PR using the GUI difftool:
$ git pr show -t 3809
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3809.diff