From: David Miller <davem@davemloft.net>
To: gerrit@erg.abdn.ac.uk
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: IPV6_PKTINFO socket option
Date: Wed, 08 Aug 2007 15:02:48 -0700 (PDT) [thread overview]
Message-ID: <20070808.150248.124083797.davem@davemloft.net> (raw)
In-Reply-To: <200708081216.51283@strip-the-willow>
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Date: Wed, 8 Aug 2007 12:16:51 +0100
> 2. On sparc64 with the same kernel IPV6_PKTINFO works without problems, even pulls
> out the cmsg fields correctly. Conversely, when trying to set the IPV6_RECVPKTINFO
> sticky option on the socket, no cmsg fields are generated.
> The kernel is of the same date and revision as the i386 kernel - library issue ???
> It is very annoying, since the application needs to run on both architectures.
Almost certainly a compat layer bug in the kernel, it would
affect 32-bit applications on powerpc64 and similar if so.
prev parent reply other threads:[~2007-08-08 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 11:16 IPV6_PKTINFO socket option Gerrit Renker
2007-08-08 22:02 ` David Miller [this message]
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=20070808.150248.124083797.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerrit@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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 NNTP newsgroup(s).