From: Steffen Moser <lists@steffen-moser.de>
To: David R <david@unsolicited.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.14 and old versions of traceroute
Date: Tue, 1 Nov 2005 12:20:08 +0100 [thread overview]
Message-ID: <20051101112008.GR22057@steffen-moser.de> (raw)
In-Reply-To: <fa.e5044g2.p4421e@ifi.uio.no>
Hi David,
* On Mon, Oct 31, 2005 at 07:30 PM (+0000), David R wrote:
> 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 am experiencing exactly the same problem with traceroute-0.6.2
running on SuSE 10.0 together with kernel 2.6.14. The whole thing
happens on a single core dual Opteron machine. I've tested this
kernel version on that machine only, yet.
I've also tried the latest traceroute version (1.0.2) from
ftp://ftp.lst.de/pub/people/okir/traceroute/
and experienced the same behaviour.
Olaf Kirch has just sent me a patch against 2.6.14. It has also
been discussed in NETDEV.
This fixed it for me:
--- a/net/core/datagram.c 2005-11-01 11:38:31.000000000 +0100
+++ b/net/core/datagram.c 2005-11-01 11:38:45.000000000 +0100
@@ -213,6 +213,10 @@
{
int i, err, fraglen, end = 0;
struct sk_buff *next = skb_shinfo(skb)->frag_list;
+
+ if (!len)
+ return 0;
+
next_skb:
fraglen = skb_headlen(skb);
i = -1;
Bye,
Steffen
next parent reply other threads:[~2005-11-01 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.e5044g2.p4421e@ifi.uio.no>
2005-11-01 11:20 ` Steffen Moser [this message]
2005-10-31 19:29 David R
2005-10-31 19:50 ` Chris Boot
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=20051101112008.GR22057@steffen-moser.de \
--to=lists@steffen-moser.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®