From: Brian Haley <brian.haley@hp.com>
To: Steve Chen <schen@mvista.com>
Cc: usagi-users-ctl@ml.linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: TAHI CN-6-4-1 failed on Linux 2.6.32 kernel
Date: Thu, 12 Aug 2010 22:23:46 -0400 [thread overview]
Message-ID: <4C64ACB2.3090600@hp.com> (raw)
In-Reply-To: <AANLkTik5JOupTW97ikf1imsZrkmwgfPNsvBoSZp1S8JV@mail.gmail.com>
On 08/12/2010 07:04 PM, Steve Chen wrote:
> On Thu, Aug 12, 2010 at 4:10 PM, Brian Haley <brian.haley@hp.com> wrote:
>> Hi Steve,
>>
>> On 07/28/2010 11:20 PM, Steve Chen wrote:
>>> Hello,
>>>
>>> The TAHI correspondent node tests CN-6-4-1 (Processing in upper layer
>>> - Echo Checksum) failed for me in the 2.6.32 kernel. It appears that
>>> the Linux kernel is replying the ICMP echo request in
>>> icmpv6_echo_reply without much checking. Is this an intentional
>>> non-conformance to RFC3775 section 9.3.1?
>>
>> Sorry for the late reply. I've run these tests in the past against
>> SLES11 (2.6.27 ?) back in January 2009 and this one passed from looking
>> at my logs. I don't have that system around anymore to check the config,
>> etc. I didn't see any obvious commit that would have broken it from a
>> quick look, do you have a test setup to do some debugging? It will
>> take a little time for me to re-configure mine to run this test.
>
> Brian,
>
> I'm using mip6d from git://www.umip.org/git/umip.git commit id
> d1c240f3deb690af902ce1ff128780551ff6141c. Is that the correct version
> to use? Looking at the kernel code again, the checksum error should
> have been caught in icmpv6_rcv. There are probably something wrong
> with my setup. I'll dig around a bit more.
The system has long since been dismantled, so I'm not sure what version
of mip6d I used. Yes, icmpv6_rcv() does check for checksum errors, it
would be good to print-out three addresses to see which one is which,
in case they weren't swapped correctly or something. It would be good
to know what value skb->ip_summed was too, as a start.
> Tests 5-3-1 to 5-3-6 also failed for me. Did they pass for you?
I had no failures, but 5 warnings (2-1-6, 2-3-11, 4-7-1, 5-4-2, and
6-3-1). I'll see if I can get a CN test run done on my current
config.
-Brian
next prev parent reply other threads:[~2010-08-13 2:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 3:20 TAHI CN-6-4-1 failed on Linux 2.6.32 kernel Steve Chen
2010-08-12 21:10 ` Brian Haley
2010-08-12 23:04 ` Steve Chen
2010-08-13 0:00 ` Steve Chen
2010-08-13 2:23 ` Brian Haley [this message]
2010-08-13 17:34 ` Steve Chen
2010-08-13 17:55 ` Brian Haley
2010-08-13 22:25 ` Steve Chen
2010-08-16 14:07 ` Steve Chen
2010-08-19 18:35 ` Steve Chen
2010-08-20 0:06 ` David Miller
2010-08-20 17:16 ` Steve Chen
2010-08-20 17:39 ` Jesse Gross
[not found] ` <AANLkTi=T_=Dy8EhOOyevLd4yj1cy2P8ytXUPS=Y-d6hK@mail.gmail.com>
2010-08-21 4:16 ` Steve Chen
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=4C64ACB2.3090600@hp.com \
--to=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=schen@mvista.com \
--cc=usagi-users-ctl@ml.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 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.