From: David R <david@unsolicited.net>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.14 and old versions of traceroute
Date: Mon, 31 Oct 2005 19:29:15 +0000 [thread overview]
Message-ID: <4366708B.4080900@unsolicited.net> (raw)
I've noticed that old versions of traceroute no longer work properly
with the latest kernel. 2.6.13.4 is OK. I've done a bit of strace and am
posting the differences here. These are from a 64 bit kernel using
traceroute 0.6.2 as shipped with most versions of SuSE. I have confirmed
that the same problem is present in a 32 bit kernel on a different
machine. A later traceroute 1.4a12 works properly.
2.6.13.4
poll([{fd=6, events=POLLERR, revents=POLLERR}, {fd=3, events=POLLERR},
{fd=4, events=POLLERR}, {fd=5, events=POLLERR}], 4, 1) = 1
recvmsg(6, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33443),
sin_addr=inet_addr("69.10.132.115")}, msg_iov(0)=[], msg_controllen=80,
{cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=0x1d /* SCM_??? */, ...},
msg_flags=MSG_ERRQUEUE}, MSG_ERRQUEUE) = 0
2.6.14
poll([{fd=3, events=POLLERR, revents=POLLERR}, {fd=4, events=POLLERR},
{fd=5, events=POLLERR}, {fd=6, events=POLLERR}, {fd=7, events=POLLERR},
{fd=8, events=POLLERR}], 6, 1) = 1
recvmsg(3, 0x7fffffa30960, MSG_ERRQUEUE) = -1 EAGAIN (Resource
temporarily unavailable)
....
....
poll([{fd=3, events=POLLERR, revents=POLLERR}, {fd=4, events=POLLERR,
revents=POLLERR}, {fd=5, events=POLLERR}, {fd=6, events=POLLERR}, {fd=7,
events=POLLERR}, {fd=8, events=POLLERR}, {fd=9, events=POLLERR}], 7, 1) = 2
recvmsg(3, 0x7fffffa30960, MSG_ERRQUEUE) = -1 EAGAIN (Resource
temporarily unavailable)
recvmsg(4, 0x7fffffa30960, MSG_ERRQUEUE) = -1 EFAULT (Bad address)
I'm up for more diagnostics if necessary.
Cheers
David
next reply other threads:[~2005-10-31 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 19:29 David R [this message]
2005-10-31 19:50 ` Kernel 2.6.14 and old versions of traceroute Chris Boot
[not found] <fa.e5044g2.p4421e@ifi.uio.no>
2005-11-01 11:20 ` Steffen Moser
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=4366708B.4080900@unsolicited.net \
--to=david@unsolicited.net \
--cc=linux-kernel@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.