public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christoph dot stueckjuergen at siemens dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1067] New: recvmsg, sendmsg broken on 64 bit architectures due to different struct msghdr definition in glibc and Linux kernel
Date: Thu, 14 Jul 2005 08:58:00 -0000	[thread overview]
Message-ID: <20050714085810.1067.christoph.stueckjuergen@siemens.com> (raw)

recvmsg and sendmsg are broken on 64-bit architectures due to different  
definitions of struct msghdr in the Linux kernel (2.6.12) and the glibc  
(2.3.5).   
  
In the kernel <linux/socket.h>:  
struct msghdr {  
	void	*	msg_name;  
	int		msg_namelen;  
	struct iovec *	msg_iov;	  
	__kernel_size_t	msg_iovlen;  
	void 	*	msg_control;  
	__kernel_size_t	msg_controllen;  
	unsigned	msg_flags;  
};  
  
In the glibc <bits/socket.h>:  
struct msghdr  
  {  
    void *msg_name;        
    socklen_t msg_namelen;  
    struct iovec *msg_iov;  
    int msg_iovlen;         
    void *msg_control;      
    socklen_t msg_controllen;  
    int msg_flags;             
  };  
  
msg_iovlen and msg_controllen are 64 bit wide in the kernel header and 32 bit  
wide in the glibc header.

-- 
           Summary: recvmsg, sendmsg broken on 64 bit architectures due to
                    different struct msghdr definition in glibc and Linux
                    kernel
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: christoph dot stueckjuergen at siemens dot com
                CC: glibc-bugs at sources dot redhat dot com
  GCC host triplet: mips64-linux-gnu
GCC target triplet: mips64-linux-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1067

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-07-14  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  8:58 christoph dot stueckjuergen at siemens dot com [this message]
2005-07-14  9:03 ` [Bug libc/1067] " jakub at redhat dot com
2005-07-14  9:06 ` christoph dot stueckjuergen at siemens dot com
2005-07-14  9:12 ` jakub at redhat dot com
2005-12-30  9:27 ` cvs-commit at gcc dot gnu dot org
2005-12-30  9:28 ` aj at suse dot de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050714085810.1067.christoph.stueckjuergen@siemens.com \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).