Description
The documentation states that the driver return -ENOBUFS when recv() was called with a buffer too small to hold the incoming frame. But two questions are remain to be decided:
- Should the frame be dropped in that case implicitly? Or should the upper layer decide by either asking the driver to drop the frame explicitly in a subsequent call, or by providing a bigger buffer in a subsequent call?
- Should the part of the frame fitting in the buffer still be retrieved?
Also: Some drivers seem to silently truncate the frame in this case instead of returning an error. This should be tracked an fixed. I suggest to first decide on the questions above and than make sure that all drivers comply with this API
Description
The documentation states that the driver return
-ENOBUFSwhenrecv()was called with a buffer too small to hold the incoming frame. But two questions are remain to be decided:Also: Some drivers seem to silently truncate the frame in this case instead of returning an error. This should be tracked an fixed. I suggest to first decide on the questions above and than make sure that all drivers comply with this API