From: Steve Rago <sar@nec-labs.com>
To: David Miller <davem@davemloft.net>
Cc: <luto@amacapital.net>, <netdev@vger.kernel.org>,
<mtk.manpages@gmail.com>, <ebiederm@xmission.com>
Subject: Re: bug in passing file descriptors
Date: Mon, 7 Oct 2013 16:29:15 -0400 [thread overview]
Message-ID: <5253199B.3000109@nec-labs.com> (raw)
In-Reply-To: <20131007.154226.533738557474978526.davem@davemloft.net>
On 10/07/2013 03:42 PM, David Miller wrote:
> There is no compatability issue.
>
> 32-bit tasks will always see the 4-byte align/length.
> 64-bit tasks will always see the 8-byte align/length.
>
Really? So when I compile my application on a 32-bit Linux box and then try to run it on a 64-bit Linux box, you're not
going to overrun my buffer when CMSG_SPACE led me to allocate an insufficient amount of memory needed to account for
padding on the 64-bit platform?
By the way, FreeBSD, Mac OS X, and Solaris all behave as I described, so if you're happy with Linux behaving
differently, then I'll stop wasting bandwidth.
Steve
next prev parent reply other threads:[~2013-10-07 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 18:27 bug in passing file descriptors Steve Rago
2013-10-07 18:44 ` Andy Lutomirski
2013-10-07 19:06 ` Steve Rago
2013-10-07 19:12 ` David Miller
2013-10-07 19:17 ` Steve Rago
2013-10-07 19:42 ` David Miller
2013-10-07 20:29 ` Steve Rago [this message]
2013-10-07 21:32 ` David Miller
2013-10-07 22:55 ` Andi Kleen
2013-10-08 14:32 ` Steve Rago
2013-10-08 16:02 ` Andy Lutomirski
2013-10-08 16:18 ` Steve Rago
2013-10-08 16:41 ` Andi Kleen
2013-10-08 16:51 ` Steve Rago
2013-10-09 14:07 ` Steve Rago
2013-10-08 8:43 ` David Laight
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=5253199B.3000109@nec-labs.com \
--to=sar@nec-labs.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=luto@amacapital.net \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.