Re: Question on rhashtable in worst-case scenario.

From: Ben Greear
Date: Wed Mar 30 2016 - 12:52:31 EST

On 03/30/2016 09:38 AM, David Miller wrote:
From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
Date: Wed, 30 Mar 2016 11:14:12 +0200

On Tue, 2016-03-29 at 09:16 -0700, Ben Greear wrote:
Looks like rhashtable has too much policy in it to properly deal with
cases where there are too many hash collisions, so I am going to work
on reverting it's use in mac80211.

I'm not really all that happy with that approach - can't we fix the
rhashtable? It's a pretty rare corner case that many keys really are
identical and no kind of hash algorithm, but it seems much better to
still deal with it than to remove the rhashtable usage and go back to
hand-rolling something.

Yeah reverting seems like a really idiotic way to deal with the issue.

If someone can fix rhashtable, then great.
I read some earlier comments [1] back when someone else reported
similar problems, and the comments seemed to indicate that rhashtable was
broken in this manner on purpose to protect against hashing attacks.

If you are baking in this type of policy to what should be a basic
data-type, then it is not useful for how it is being used in
the mac80211 stack.



Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc