You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the sendmsg function it is possible to send a UDP packet by collecting the payload from different parts of memory . This can be done by providing a msghdr to sendmsg with an msg_iovlen>1. However, it seems like DCE will send a packet for each memory location specified.
The patch below solved the problem for me for the particular application I was porting. I haven not looked deeply into this so there may be issues / other things that need to be fixed as well. As an example, there seems to be a similar problem when receiving a UDP packet (I have not tested this particular patch as I have manually reconstructed it from another patch I did test).
Using the sendmsg function it is possible to send a UDP packet by collecting the payload from different parts of memory . This can be done by providing a msghdr to sendmsg with an msg_iovlen>1. However, it seems like DCE will send a packet for each memory location specified.
The patch below solved the problem for me for the particular application I was porting. I haven not looked deeply into this so there may be issues / other things that need to be fixed as well. As an example, there seems to be a similar problem when receiving a UDP packet (I have not tested this particular patch as I have manually reconstructed it from another patch I did test).
The text was updated successfully, but these errors were encountered: