socket: stop setting vector length inside read_mhdr

CMSG_FIRSTHDR/CMSG_NEXTHDR operate in terms of pointers contained
inside msghdr structure, vector capacity doesn't matter for them.

This would change external behavior of recvmsg/recvmmsg in a sense
that buffer passed to store controll messages won't have it's length
updated but intended way to receive control messages is with cmsgs
iterator on `RecvMsg` which would still work.

This change is required to allow using a single vector to store
control messages from multiple packets

0 files changed, 0 insertions, 0 deletions