diff options
author | Tom Herbert <tom@herbertland.com> | 2016-03-07 14:11:10 -0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-03-09 16:36:15 -0500 |
commit | 7ced95ef525c329f947c424859cf2b0a3b731f8c (patch) | |
tree | bdbbbc12cf0b1b82f4c07b36d1c45262c2dd3af3 /net/ipv4/protocol.c | |
parent | f29698fc6b3a45a5c6147eca8379f38be8232117 (diff) |
kcm: Add memory limit for receive message construction
Message assembly is performed on the TCP socket. This is logically
equivalent of an application that performs a peek on the socket to find
out how much memory is needed for a receive buffer. The receive socket
buffer also provides the maximum message size which is checked.
The receive algorithm is something like:
1) Receive the first skbuf for a message (or skbufs if multiple are
needed to determine message length).
2) Check the message length against the number of bytes in the TCP
receive queue (tcp_inq()).
- If all the bytes of the message are in the queue (incluing the
skbuf received), then proceed with message assembly (it should
complete with the tcp_read_sock)
- Else, mark the psock with the number of bytes needed to
complete the message.
3) In TCP data ready function, if the psock indicates that we are
waiting for the rest of the bytes of a messages, check the number
of queued bytes against that.
- If there are still not enough bytes for the message, just
return
- Else, clear the waiting bytes and proceed to receive the
skbufs. The message should now be received in one
tcp_read_sock
Signed-off-by: Tom Herbert <tom@herbertland.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/protocol.c')
0 files changed, 0 insertions, 0 deletions