-
Notifications
You must be signed in to change notification settings - Fork 783
-
Notifications
You must be signed in to change notification settings - Fork 783
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
Worker crashes with a segmentation fault #40
Labels
severity: major
This issue is of MAJOR severity.
status: fixed
This issue is a now-fixed bug.
subsystem: http
This issue is within the HTTP subsystem.
type: bug
This issue describes a bug.
Comments
TimWolla
added
type: bug
This issue describes a bug.
status: needs-triage
This issue needs to be triaged.
labels
Feb 10, 2019
It looks like this one could be a likely candidate :
commit 56fd865
BUG/MEDIUM: stream: Don't forget to free s->unique_id in stream_free().
In stream_free(), free s->unique_id. We may still have one, because it's
allocated in log.c::strm_log() no matter what, even if it's a TCP connection
and thus it won't get free'd by http_end_txn().
(...)
However I don't see why it would be, since s->unique_id is always cleared once
freed.
|
I think I found it. The pool_free() in stream_free() doesn't reset unique_id
to null so it experiences a second free() in http_end_txn().
This patch should fix it.
diff --git a/src/stream.c b/src/stream.c
index a96ddcb..df778b1 100644
--- a/src/stream.c
+++ b/src/stream.c
@@ -387,6 +387,7 @@ static void stream_free(struct stream *s)
}
pool_free(pool_head_uniqueid, s->unique_id);
+ s->unique_id = NULL;
hlua_ctx_destroy(s->hlua);
s->hlua = NULL;
|
I can confirm that the patch fixes this issue in my test environment (where I managed to reproduce the issue). Can we get a release for that? For my production servers I prefer the original Debian packages which are affected. |
TimWolla
added
1.8
This issue affects the HAProxy 1.8 stable branch.
1.9
This issue affects the HAProxy 1.9 stable branch.
dev
This issue affects the HAProxy development branch.
status: reviewed
This issue was reviewed. A fix is required.
and removed
status: needs-triage
This issue needs to be triaged.
labels
Feb 10, 2019
On Sun, Feb 10, 2019 at 08:15:39AM -0800, Tim Düsterhus wrote:
I can confirm that the patch fixes this issue
Thanks for the test, I'm committing it.
Can we get a release for that?
Let's wait a few more days to be sure we don't miss anything else. Too
many versions in little time cause more confusion than anything.
|
TimWolla
added
severity: major
This issue is of MAJOR severity.
status: fixed
This issue is a now-fixed bug.
and removed
dev
This issue affects the HAProxy development branch.
status: reviewed
This issue was reviewed. A fix is required.
1.9
This issue affects the HAProxy 1.9 stable branch.
1.8
This issue affects the HAProxy 1.8 stable branch.
labels
Feb 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
severity: major
This issue is of MAJOR severity.
status: fixed
This issue is a now-fixed bug.
subsystem: http
This issue is within the HTTP subsystem.
type: bug
This issue describes a bug.
Output of
haproxy -vv
anduname -a
What's the configuration?
Steps to reproduce the behavior
Actual behavior
GDB Stack from prod:
Expected behavior
Don't crash.
Do you have any idea what may have caused this?
Will add once I have more information.
Do you have an idea how to solve the issue?
Will add once I have more information.
The text was updated successfully, but these errors were encountered: