From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH RFC] ipv6: use stronger hash for reassembly queue hash table
Date: Fri, 8 Mar 2013 16:08:31 +0100 [thread overview]
Message-ID: <20130308150831.GD28531@order.stressinduktion.org> (raw)
In-Reply-To: <1362754386.15793.226.camel@edumazet-glaptop>
On Fri, Mar 08, 2013 at 06:53:06AM -0800, Eric Dumazet wrote:
> No matter how you hash, a hacker can easily fill your defrag unit with
> not complete datagrams, so what's the point ?
I want to harden reassembly logic against all fragments being put in
the same hash bucket because of malicious traffic and thus creating
long list traversals in the fragment queue hash table.
I totally agree that fragments should be avoided if possible.
Thanks,
Hannes
next prev parent reply other threads:[~2013-03-08 15:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 21:42 [PATCH RFC] ipv6: use stronger hash for reassembly queue hash table Hannes Frederic Sowa
2013-03-08 5:57 ` Hannes Frederic Sowa
2013-03-08 13:04 ` Hannes Frederic Sowa
2013-03-08 14:53 ` Eric Dumazet
2013-03-08 15:08 ` Hannes Frederic Sowa [this message]
2013-03-08 15:23 ` Eric Dumazet
2013-03-08 15:54 ` Hannes Frederic Sowa
2013-03-08 16:15 ` Eric Dumazet
2013-03-08 16:18 ` Hannes Frederic Sowa
2013-03-09 15:19 ` Hannes Frederic Sowa
2013-03-08 20:53 ` Hannes Frederic Sowa
2013-03-13 1:27 ` Hannes Frederic Sowa
2013-03-13 1:31 ` Hannes Frederic Sowa
2013-03-13 5:29 ` Eric Dumazet
2013-03-14 1:37 ` Hannes Frederic Sowa
2013-03-14 4:36 ` Stephen Hemminger
2013-03-14 7:14 ` Hannes Frederic Sowa
2013-03-14 9:47 ` David Laight
2013-03-14 10:34 ` Eric Dumazet
2013-03-14 12:34 ` Hannes Frederic Sowa
2013-03-14 7:10 ` Jesper Dangaard Brouer
2013-03-14 7:23 ` Hannes Frederic Sowa
2013-03-14 7:28 ` Hannes Frederic Sowa
2013-03-14 9:18 ` Jesper Dangaard Brouer
2013-03-14 12:45 ` Hannes Frederic Sowa
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=20130308150831.GD28531@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=eric.dumazet@gmail.com \
--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).