-
Notifications
You must be signed in to change notification settings - Fork 103
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
TfwStream objects leaks if errors happen on serving h2 clients #1377
Comments
under wrk workload running from the host system.
Tempesta config (the backend server services the tempesta-tech.com site):
Crash
Fixed in #1643 |
Another incarnation of this bug was catched by a user.
netconsole log
(this is a digest. Full log attached.) I'll post additional info here if/when succede to reproduce and analyse the case. |
Also a case (reproducible)How to reproduce
Events in the traceAll begin when the test
This happend at the line:
As a result, the request is dropped.
This happens at the line
at the line
|
Some analytics on the wayhttp_stream.h:
Where the However the only calls of these functions are located in:
(http_frame.c) The proposal is to remove the |
Another analytics on the way
Here
whereas Seems to be a bug, moreover, a critical bug. This bug is a good candidate for a reason of The Issue, |
I'm not sure about the proposal since we have #1472 Please move #1377 (comment) and #1377 (comment) to a new task for https://github.com/tempesta-tech/tempesta/milestone/11 milestone. The original user report and my scenario did not involve HTTP/2 at all, this is pure HTTP/1 over TLS problem. Please observe #1422 "tfw_cli_cache() allocates HTTP/2 context even for HTTP/1 connections". I reckon the bug is much simpler. |
I have repeated this test #1377 (comment) Everything works fine. |
Additionaly I have insert the catcher ( Realy |
(the response from artificaly inserted WARN_ON(1) catcher). |
Ghkm.. I am confised a little... It seems there are different bugs. |
|
which is WARN_ON_ONCE(tcb->seq + skb->len + !!(tcb->tcp_flags & TCPHDR_FIN)
!= tcb->end_seq); |
|
|
UPD this is just an invalid message printed when a peer closes TLS connection, removed in a2b71ce |
Quote
I get like trace for tests long body and mtu 80 DMESG
|
I believe the initial problem, which was: Since we don't delete |
I've rechecked all the warnings on TFW master branch from 12 Jan 2021 using tempesta-test de0cbb8 and then ran the same tests on #1777. |
Scope
Testing
No special tests are required for this particular error. Just need to assure that no warnings are triggered during h2 tests. Like we do so for HTTP/1.1 tests.
The text was updated successfully, but these errors were encountered: