From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>, captwiggum@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: TAHI testing fails for IPv6 Fragments in Kernel 4.9
Date: Wed, 6 Mar 2019 14:34:25 -0800 [thread overview]
Message-ID: <4be8c46a-6231-6e7b-8cd7-0a2efab07caa@gmail.com> (raw)
In-Reply-To: <20190306.142818.1045935324715292108.davem@davemloft.net>
On 03/06/2019 02:28 PM, David Miller wrote:
> From: Captain Wiggum <captwiggum@gmail.com>
> Date: Wed, 6 Mar 2019 15:26:43 -0700
>
>> We are using the TAHI Self-test tools from IPv6 Ready Logo Program:
>> https://www.ipv6ready.org/?page=documents&tag=ipv6-core-protocols
>>
>> The test passed up to 4.9.133, then fails ever since.
>>
>> The are about 20 failing test cases regarding IPv6 fragments,
>> where the kernel is issuing an ICMPv6 parameter problem pointing
>> to the Fragmentation Header.
>>
>> I see lots of commits regarding improving fragment processing.
>> Has anyone else run TAHI tests on kernel 4.9 or later?
>> Is there any interest in looking into this to improve
>> the IPv6 functionality?
>
> It is intentionally failing those tests to fix a denial of service
> issue with ipv6 fragmentation and this will therefore not be changed.
That was Florian patch that was later reverted, right ?
0ed4229b08c13c84a3c301a08defdc9e7f4467e6 ipv6: defrag: drop non-last frags smaller than min mtu
-> reverted in
d4289fcc9b16b89619ee1c54f829e05e56de8b9a net: IP6 defrag: use rbtrees for IPv6 defrag
next prev parent reply other threads:[~2019-03-06 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 22:26 TAHI testing fails for IPv6 Fragments in Kernel 4.9 Captain Wiggum
2019-03-06 22:28 ` David Miller
2019-03-06 22:34 ` Eric Dumazet [this message]
2019-03-06 22:50 ` David Miller
2019-03-06 22:51 ` Captain Wiggum
2019-03-12 4:12 ` Captain Wiggum
2019-03-12 4:18 ` Captain Wiggum
2019-03-12 4:20 ` Eric Dumazet
2019-03-12 4:29 ` Captain Wiggum
2019-03-06 22:29 ` Florian Fainelli
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=4be8c46a-6231-6e7b-8cd7-0a2efab07caa@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=captwiggum@gmail.com \
--cc=davem@davemloft.net \
--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 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).