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

Detect and report overlapping Read chunks #6

Open
chucklever opened this issue Mar 19, 2020 · 1 comment
Open

Detect and report overlapping Read chunks #6

chucklever opened this issue Mar 19, 2020 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@chucklever
Copy link
Owner

Is it possible for a requester to form an RPC/RDMA message where a byte-range appears in more than one Read chunk? For example, suppose there are two Read chunks in a message:

  • Inline: 32 bytes
  • Chunk A: 8 bytes at position 16
  • Chunk B: 8 bytes at position 24

Chunk B starts in the middle of chunk A. How is the responder going to re-assemble this message? If it can't, how does it report that the message is unparsable? ERR_CHUNK / RDMA2_ERR_BAD_XDR is probably the right choice.

The question is whether a more specific error response is needed from the responder. Probably no: this is not expected to be a frequent error condition, and it is the sign of a broken requester implementation, rather than an exigent circumstance.

However, it might be proper and helpful if the document guided responder implementors to check for this particular case.

@chucklever chucklever added the question Further information is requested label Mar 19, 2020
@chucklever chucklever self-assigned this Mar 19, 2020
@chucklever
Copy link
Owner Author

How about the case where a Read segment is at a position that is beyond the end of the message?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant