Skip to content
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

rdma: (fix) memory leak: don't alloc recv_conn_resp_req on EAGAIN #388

Merged
merged 1 commit into from
Apr 13, 2024

Conversation

rauteric
Copy link
Contributor

@rauteric rauteric commented Apr 13, 2024

Move call to prepare_recv_conn_resp_req before entry point of COMM_SEND_CONN stage.

This resolves a potential memory leak where prepare_recv_conn_resp_req is called multiple times on EAGAIN.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@rauteric rauteric requested a review from a team as a code owner April 13, 2024 00:00
@rajachan rajachan requested a review from AmedeoSapio April 13, 2024 00:01
@rauteric rauteric force-pushed the fix-eagain-memory-leak branch from 8a2ac95 to 3dc0cd1 Compare April 13, 2024 00:02
AmedeoSapio
AmedeoSapio previously approved these changes Apr 13, 2024
Move call to `prepare_recv_conn_resp_req` before entry point of
`COMM_SEND_CONN` stage.

This resolves a potential memory leak where `prepare_recv_conn_resp_req`
is called multiple times on EAGAIN.

Also fixup a similar case in `accept`, although there was no memory
allocation there so no leak.

Signed-off-by: Eric Raut <[email protected]>
@rauteric
Copy link
Contributor Author

Fixed a similar case in accept, although that one didn't allocate any memory so not a leak.

@rajachan rajachan merged commit 398b853 into aws:master Apr 13, 2024
13 checks passed
@rauteric rauteric deleted the fix-eagain-memory-leak branch April 18, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants