-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fixes #6072 - jetty server high CPU when client sends TLS record length > 17408 (jetty-10.0.x) #6074
Conversation
…408. Avoid spinning if the input buffer is full. Signed-off-by: Simone Bordet <simone.bordet@gmail.com> Co-authored-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Forward port of #6073 |
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.
changed my mind. I think we should check space on any 0 fill
jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java
Outdated
Show resolved
Hide resolved
…408. Updates after review. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
|
||
// Sleep to see if the server spins. | ||
Thread.sleep(1000); | ||
assertThat(unwraps.get(), lessThan(128L)); |
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 would move the assertion out of the try-with-resource
block as the IO.readBytes
call already would wait 1s if this bug is triggered.
…408.
Avoid spinning if the input buffer is full.
Signed-off-by: Simone Bordet simone.bordet@gmail.com
Co-authored-by: Joakim Erdfelt joakim.erdfelt@gmail.com