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

Potential issue w/ lifetime of RDMA async read buffers #160

Open
TylerADavis opened this issue Aug 24, 2017 · 1 comment
Open

Potential issue w/ lifetime of RDMA async read buffers #160

TylerADavis opened this issue Aug 24, 2017 · 1 comment

Comments

@TylerADavis
Copy link
Collaborator

Currently the buffer that an asynchronous RDMA read reads into has its lifetime tied to the future returned by the operation. This has been working so far, but it seems possible that if the future returned by the function were to go out of scope before the read operation completed that buffer to read into would be deallocated, resulting in the read operation potentially overwriting memory in use elsewhere.

It may be beneficial to find a way of tying the lifetime of the receive buffer to the asynchronous operation (perhaps place a shared pointer inside of RDMAOpInfo).

@TylerADavis
Copy link
Collaborator Author

Another alternative would be to place a shared pointer inside of RDMAMem, but that doesn't seem very clean either.

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

No branches or pull requests

1 participant