This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/16919] recvmsg standard compliance
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 07 May 2014 23:23:58 +0000
- Subject: [Bug libc/16919] recvmsg standard compliance
- Auto-submitted: auto-generated
- References: <bug-16919-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16919
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 7 May 2014, sickmind at i2pmail dot org wrote:
> Thanks for the tip. I should create appropriate __libc_{sendmsg,recvmsg}
> functions for that, am I right?
Exactly what's appropriate depends on the details of the interfaces - what
libc interfaces use these structures as inputs, outputs or both, and what
kernel interfaces libc uses with them (and again, whether as inputs,
outputs or both), and how the kernel handles the high bits in question.
The patch submission (to libc-alpha, see the contribution checklist on the
wiki) will need to contain a detailed analysis of those issues that
justifies why the changes in the patch don't cause any problems for
existing binaries or cause the kernel interface to be used incorrectly.
If you write up that analysis before implementing the patch, it may help
people advise on what should or should not be in the patch.
--
You are receiving this mail because:
You are on the CC list for the bug.