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.

Sign up for GitHub

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

Jump to bottom

msghdr flag MSG_TRUNC not set #200

Closed
iangudger opened this issue Apr 17, 2019 · 2 comments
Closed

msghdr flag MSG_TRUNC not set #200

iangudger opened this issue Apr 17, 2019 · 2 comments
Assignees
@iangudger

Comments

@iangudger
Copy link
Contributor

recvmsg should set the flags field in the passed msghdr with MSG_TRUNC when appropriate. It currently always sets flags to 0.
@iangudger iangudger self-assigned this Apr 17, 2019
@chuangxueli
Copy link

yes,we are also following this question,and the control data is not delivered to the lower layer in socket

@iangudger
Copy link
Contributor Author

@chuangxueli If you are having a problem with control messages, please file a separate issue. This issue is only about setting the MSG_TRUNC flag. I have a CL out which fixes this issue if you want to try it: gvisor.dev/cl/16881

@iangudger iangudger mentioned this issue Apr 19, 2019
Closed
tonistiigi pushed a commit to tonistiigi/gvisor that referenced this issue May 3, 2019
@iangudger @shentubot
Add support for the MSG_TRUNC msghdr flag.
509c5aa 
The MSG_TRUNC flag is set in the msghdr when a message is truncated.

Fixes google#200

PiperOrigin-RevId: 244440486
Change-Id: I03c7d5e7f5935c0c6b8d69b012db1780ac5b8456
Upstream-commit: 358eb52
@snyk-bot snyk-bot mentioned this issue Mar 5, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iangudger iangudger

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iangudger @chuangxueli